<?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>Why your application fails to load after building with a new version of VS?</title><link>http://blogs.msdn.com/vcblog/archive/2007/07/02/why-your-application-fails-to-load-after-building-with-a-new-version-of-vs.aspx</link><description>In this blog post I would like to outline how the build decides the CRT dependencies and what that means to the user. This basic trouble shooting guide should come in handy for diagnosing dependency errors. Please note that Nikola's blog is an awesome</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Granville Barnett July 2007</title><link>http://blogs.msdn.com/vcblog/archive/2007/07/02/why-your-application-fails-to-load-after-building-with-a-new-version-of-vs.aspx#3669271</link><pubDate>Tue, 03 Jul 2007 12:45:43 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3669271</guid><dc:creator>Granville Barnett July 2007</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://gbarnett.org/2007/07/03/visual-c-team-blog-why-your-application-fails-to-load-after-building-with-a-new-version-of-vs.html"&gt;http://gbarnett.org/2007/07/03/visual-c-team-blog-why-your-application-fails-to-load-after-building-with-a-new-version-of-vs.html&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Why your application fails to load after building with a new version of VS?</title><link>http://blogs.msdn.com/vcblog/archive/2007/07/02/why-your-application-fails-to-load-after-building-with-a-new-version-of-vs.aspx#3835012</link><pubDate>Thu, 12 Jul 2007 21:22:16 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3835012</guid><dc:creator>sarath(nscbabu@gmail.com)</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Suppose I have a 32 bit version of my .lib file as well as 64 bit version of my .lib file in different folders and my 32 bit application points to both the paths how does the linker work?&lt;/p&gt;
&lt;p&gt;--sarath.&lt;/p&gt;
</description></item><item><title>re: Why your application fails to load after building with a new version of VS?</title><link>http://blogs.msdn.com/vcblog/archive/2007/07/02/why-your-application-fails-to-load-after-building-with-a-new-version-of-vs.aspx#4530185</link><pubDate>Thu, 23 Aug 2007 22:17:40 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4530185</guid><dc:creator>Ale Contenti</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I assume the two libs have the same name. The linker will pick up the first lib it sees on the LIB path. Usually, when you compile for 32bits and 64bits you use two different sets of PATH, LIB, INCLUDE environment variables.&lt;/p&gt;
&lt;p&gt;The VC++ projects in the IDE already do that for you for the CRT import and static libs and for the Windows import libs.&lt;/p&gt;
&lt;p&gt;Are you experiencing any problem?&lt;/p&gt;
&lt;p&gt;HTH,&lt;/p&gt;
&lt;p&gt;Ale Contenti&lt;/p&gt;
&lt;p&gt;VC++ Libraries Dev Lead&lt;/p&gt;
</description></item></channel></rss>