I can confirm what John says. I actually have VS 2005 installed (as well as a few later VS versions), and attempts to connect to SQL 2008 or SQL 2014 produced exactly that error message.
I would say that there is all reason to move to a newer version of both Visual Studio and SQL Server.