If you’re running a mixed team of developers with different versions of Visual Studio, you’re going to run into problems with solution and project file version compatibility.
Theoretically, Visual Studio 2012 changed that; all solution and project files are backwards compatible! Yay! Problem solved.
Except for our old friend .dbproj from Visual Studio 2010.
Visual Studio 2012 converts .dbproj files into .sqlproj files, which Visual Studio 2010 can’t open. Google tells me that I just have to install SQL Server Data Tools for Visual Studio 2010, and everything will be great!
Except that the current version of the SQL Server Data Tools (December 2012 at the time of writing) is a higher version than that which ships with Visual Studio 2012. Visual Studio 2010 converts your .sqlproj files into the new version, and now Visual Studio 2012 can’t open them.
So, what’s a poor development manager to do? Install the updated SQL Server Data Tools for Visual Studio 2012 as well!
Go get both versions here: http://msdn.microsoft.com/en-us/data/hh297027
They run fine side by side (at least for the limited testing I’ve done), and your Visual Studio 2010 users can now be jealous of your Visual Studio 2012 users while still being able to get work done. It’s the best of both worlds, really.
- Install the latest version of SQL Server Data Tools from http://msdn.microsoft.com/en-us/data/hh297027
Open the solution in Visual Studio 2012, convert projects Open the solution in Visual Studio 2010, profit!
- Visual Studio 2010 users install the 2010 version of SQL Server Data Tools
- Visual Studio 2012 users install the 2012 version of SQL Server Data Tools
- Users with both versions install both versions of SQL Server Data Tools