<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>VSDBCMD.EXE Return Codes</title><link>http://blogs.msdn.com/b/gertd/archive/2009/07/21/vsdbcmd-exe-return-codes.aspx</link><description>Quick one based on a forum question where somebody asked how to detect if VSDBCMD.EXE failed or succeeded inside a batch file. VSDBCMD.EXE does not return a very elaborate amount of information, there are just two return values 0 and 1, where zero indicates</description><dc:language>en</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: VSDBCMD.EXE Return Codes</title><link>http://blogs.msdn.com/b/gertd/archive/2009/07/21/vsdbcmd-exe-return-codes.aspx#9993129</link><pubDate>Fri, 09 Apr 2010 13:00:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9993129</guid><dc:creator>Dav</dc:creator><description>&lt;p&gt;Gert - Im having trouble with vsdbcmd not returning 1 when an error occurs inside my generated sql file during deployment. I&amp;#39;m using the &amp;nbsp;RC of vs2010. Does the RC of vs2010 suffer from the issue fixed here: &lt;a rel="nofollow" target="_new" href="http://support.microsoft.com/kb/970595/"&gt;http://support.microsoft.com/kb/970595/&lt;/a&gt; ?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9993129" width="1" height="1"&gt;</description></item><item><title>re: VSDBCMD.EXE Return Codes</title><link>http://blogs.msdn.com/b/gertd/archive/2009/07/21/vsdbcmd-exe-return-codes.aspx#9910078</link><pubDate>Tue, 20 Oct 2009 17:55:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9910078</guid><dc:creator>dev3001</dc:creator><description>&lt;p&gt;Your blog is very helpful. I've also done a blog post in general on tracking down errors that show up during a VSDB deploy (vs a build), since you often get errors while debugging post deployment scripts and they can be elusive to track down.&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://sql-dotnet.blogspot.com/2009/10/vsdb-tracking-down-deploy-errors.html"&gt;http://sql-dotnet.blogspot.com/2009/10/vsdb-tracking-down-deploy-errors.html&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9910078" width="1" height="1"&gt;</description></item></channel></rss>