Note that there are some explanatory texts on larger screens.

plurals
  1. POCan't deploy database project - VSDBCMD deploy not seeing connection string in manifest
    text
    copied!<p>This tutorial shows how to Define a Custom Workflow to Deploy a Database from Team Foundation Build: <a href="http://msdn.microsoft.com/en-us/library/ff805001.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/ff805001.aspx</a></p> <p>However, when TFS tries to deploy my database, it complains that I must specify a connection string. I provided the .deploymanifest file as a command line parameter, and the .deploymanifest file has the connection string. </p> <p><strong>Why is VSDBCMD complaining that I haven't entered a connection string?</strong> It is also complaining about unresolved references, which are also contained in the .deploymanifest file.</p> <p>Below is the top few lines of my .deploymanifest file:</p> <pre><code> &lt;?xml version="1.0" encoding="utf-8"?&gt; &lt;Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"&gt; &lt;PropertyGroup&gt; &lt;TargetConnectionString&gt;Data Source=SQL2K8DEV;Integrated Security=True;Pooling=False&lt;/TargetConnectionString&gt; &lt;TargetDatabase&gt;Super_DB&lt;/TargetDatabase&gt; &lt;DeployToDatabase&gt;True&lt;/DeployToDatabase&gt; &lt;DeployToScript&gt;True&lt;/DeployToScript&gt; . . . </code></pre> <p><strong>EDIT:</strong> <em>The .deploymanifest file snippet above is not correct. I took that snippet from the .deploymanifest file generated by my local build, not the TFS build. The .deploymanifest generated by the TFS build was incorrect, which led me to investigate the configuration being used, which ultimately solved my problem (see answer below).</em></p> <p>And here are the errors I am getting from VSDBCMD:</p> <pre><code>C:\Program Files (x86)\Microsoft Visual Studio 10.0\VSTSDB\Deploy\VSDBCMD.EXE /a:Deploy /dd+ /dsp:Sql /manifest:RTS.deploymanifest Before you can deploy a database, you must specify a connection string in the project properties or at a command prompt. TSD\\TXDASQL2K8DEV\RTS_Deploy\DEV_Nightly_build\RTS Development Nightly Build\RTS Development Nightly Build_20111202.7\RTS.dbschema (380,7) - The reference to external elements from the source named 'Master.dbschema' could not be resolved, because no such source is loaded. </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload