<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://msmvps.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>The convoluted build configuration automation model (EnvDTE/EnvDTE80)</title><link>http://msmvps.com/blogs/carlosq/archive/2008/08/29/the-convoluted-build-configuration-of-the-automation-model-envdte-envdte80.aspx</link><description>One of the most complex things of the automation model (EnvDTE/EnvDTE80) of Visual Studio is the set of classes/properties to manage the build configurations of solutions and projects, because of the complexity itself of the configuration model of Visual</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>re: The convoluted build configuration automation model (EnvDTE/EnvDTE80)</title><link>http://msmvps.com/blogs/carlosq/archive/2008/08/29/the-convoluted-build-configuration-of-the-automation-model-envdte-envdte80.aspx#1735492</link><pubDate>Tue, 27 Oct 2009 00:37:37 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1735492</guid><dc:creator>Brandon Bloom</dc:creator><description>&lt;p&gt;This post is supremely confusing, but infinitely helpful. Thank you!&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1735492" width="1" height="1"&gt;</description></item><item><title>re: The convoluted build configuration automation model (EnvDTE/EnvDTE80)</title><link>http://msmvps.com/blogs/carlosq/archive/2008/08/29/the-convoluted-build-configuration-of-the-automation-model-envdte-envdte80.aspx#1697515</link><pubDate>Wed, 01 Jul 2009 21:10:27 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1697515</guid><dc:creator>carlosq</dc:creator><description>&lt;p&gt;It seems to me that there is no way in the automation model to do that, you will need to use some service from the Visual Studio SDK&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1697515" width="1" height="1"&gt;</description></item><item><title>re: The convoluted build configuration automation model (EnvDTE/EnvDTE80)</title><link>http://msmvps.com/blogs/carlosq/archive/2008/08/29/the-convoluted-build-configuration-of-the-automation-model-envdte-envdte80.aspx#1697513</link><pubDate>Wed, 01 Jul 2009 20:09:50 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1697513</guid><dc:creator>Sylvester Hesp</dc:creator><description>&lt;p&gt;Hi, do you happen to know whether it is possible to build a specific project for a specific platform? The SolutionBuild.BuildProject() method only accepts a string denoting the configuration, but not the platform. If I have a project for Win32 and one for x64, it will always build the Win32 version if I simply pass &amp;quot;Release&amp;quot; to that method, even though I have x64 selected as the current config. And there doesn&amp;#39;t seem to be any other Build()-like methods in the whole automation model (one on a SolutionContext would&amp;#39;ve been nice)&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1697513" width="1" height="1"&gt;</description></item><item><title>More on the build configuration automation model</title><link>http://msmvps.com/blogs/carlosq/archive/2008/08/29/the-convoluted-build-configuration-of-the-automation-model-envdte-envdte80.aspx#1649863</link><pubDate>Mon, 06 Oct 2008 11:05:36 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1649863</guid><dc:creator>Carlos Quintero (Microsoft MVP) blog</dc:creator><description>&lt;p&gt;I already wrote about the convoluted build configuration automation model and provided a visual representation&lt;/p&gt;
&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1649863" width="1" height="1"&gt;</description></item></channel></rss>