<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Main disadvantage of (really) AppLocal deployment</title>
	<link>http://blog.kalmbach-software.de/2008/05/05/main-disadvantage-of-really-applocal-deployment/</link>
	<description>Infos about Windows development and dotNET Framework</description>
	<pubDate>Thu, 09 Feb 2012 05:47:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: jkalmbach</title>
		<link>http://blog.kalmbach-software.de/2008/05/05/main-disadvantage-of-really-applocal-deployment/#comment-112</link>
		<dc:creator>jkalmbach</dc:creator>
		<pubDate>Tue, 12 Aug 2008 16:02:29 +0000</pubDate>
		<guid>http://blog.kalmbach-software.de/2008/05/05/main-disadvantage-of-really-applocal-deployment/#comment-112</guid>
		<description>Why not statically link against the CRT???
http://blog.kalmbach-software.de/2008/03/03/screencast-statically-link-to-the-c-runtime-to-prevent-vcredist-and-overcome-application-configuration-problems/</description>
		<content:encoded><![CDATA[<p>Why not statically link against the CRT???<br />
<a href="http://blog.kalmbach-software.de/2008/03/03/screencast-statically-link-to-the-c-runtime-to-prevent-vcredist-and-overcome-application-configuration-problems/" rel="nofollow">http://blog.kalmbach-software.de/2008/03/03/screencast-statically-link-to-the-c-runtime-to-prevent-vcredist-and-overcome-application-configuration-problems/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: codeplay</title>
		<link>http://blog.kalmbach-software.de/2008/05/05/main-disadvantage-of-really-applocal-deployment/#comment-111</link>
		<dc:creator>codeplay</dc:creator>
		<pubDate>Tue, 12 Aug 2008 13:46:40 +0000</pubDate>
		<guid>http://blog.kalmbach-software.de/2008/05/05/main-disadvantage-of-really-applocal-deployment/#comment-111</guid>
		<description>When we build a dll which depends on msvcp90.dll, is it possible to build the msvcp90.dll into our dll so that we don't need to deploy the msvcp90.dll.

The reason why I need this is because I am writing a firefox extension, if I put the msvcp90.dll along with my dll, it will cause the firefox have a dll loading error because firefox tries to load the msvcp90.dll.

Pls enlighten me, thanks!</description>
		<content:encoded><![CDATA[<p>When we build a dll which depends on msvcp90.dll, is it possible to build the msvcp90.dll into our dll so that we don&#8217;t need to deploy the msvcp90.dll.</p>
<p>The reason why I need this is because I am writing a firefox extension, if I put the msvcp90.dll along with my dll, it will cause the firefox have a dll loading error because firefox tries to load the msvcp90.dll.</p>
<p>Pls enlighten me, thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Mattsson</title>
		<link>http://blog.kalmbach-software.de/2008/05/05/main-disadvantage-of-really-applocal-deployment/#comment-71</link>
		<dc:creator>Michael Mattsson</dc:creator>
		<pubDate>Thu, 15 May 2008 19:21:37 +0000</pubDate>
		<guid>http://blog.kalmbach-software.de/2008/05/05/main-disadvantage-of-really-applocal-deployment/#comment-71</guid>
		<description>&#62;&#62;So I fear, that Microsoft will
&#62;&#62; remove or deprecate static linking in the next version of VS

That really doesn't seem to be likely.  Purposefully crippling their compiler and/or runtime libraries simply just isn't in the cards at Microsoft.

The reason that you don't find much info about using MS specific runtime libraries local to the app is that MS wants to discourage the practice for that average programmer.... which is fine and probably a good thing.
But there have been articles about removing the public key from manifests on MSDN and elsewhere on the internet  in the past for those who needed to do so.</description>
		<content:encoded><![CDATA[<p>&gt;&gt;So I fear, that Microsoft will<br />
&gt;&gt; remove or deprecate static linking in the next version of VS</p>
<p>That really doesn&#8217;t seem to be likely.  Purposefully crippling their compiler and/or runtime libraries simply just isn&#8217;t in the cards at Microsoft.</p>
<p>The reason that you don&#8217;t find much info about using MS specific runtime libraries local to the app is that MS wants to discourage the practice for that average programmer&#8230;. which is fine and probably a good thing.<br />
But there have been articles about removing the public key from manifests on MSDN and elsewhere on the internet  in the past for those who needed to do so.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

