CODEWITHSUNDEEP
sql-server-2008tfsvisual-studio-2013
asahun
asahun

Reputation: 195

Visual studio 2013 deploying sql server 2008 database project

I have recently migrated my visual studio 2010 projects to 2013 but my database project looks unhappy about it. I have a TFS build definition which helps me deploy the database project and i have specified the (.sln) solution file and the .proj separate file which helps e drop the file to some location. This has been working well when I was using 2010 but right now its giving me the following error.

The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.

I replaced .sln file with the .sqlproj and this seems to fix the failing build definition but I don't get any deployment files. Do you have any suggestions please, this is blocking my work right now.

Upvotes: 0

Views: 956

Answers (1)

Kevin Cunnane
Kevin Cunnane

Reputation: 8110

You need to set the environment variable VisualStudioVersion=12.0 when building from the command line if you are using VS2013. SQL Projects rely on this to detect whether to use the VS2012 (v11.0) or VS2013 (v12.0) targets file when building.

Normally when a new Visual Studio version is released there's an accompanying .Net version update that changes the default VisualStudioVersion default value, but with VS2013 this didn't happen. Hence SQL Projects (and some other resources with similar version-specific dependencies) require 12.0 to be explicitly set as the version, since 11.0 is the default.

Also when running on a build server you must have a version of Visual Studio 2013 installed that includes the SQL Server tools. Full instructions on setting up a build server are in the whitepaper and presentation on the SQL Server tools team blog.

Upvotes: 2

Related Questions