<?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>Things you shouldn't do, part 2: Dll's can't ever call CoInitialize* on the application's thread.</title><link>http://blogs.msdn.com/larryosterman/archive/2004/05/12/130541.aspx</link><description>When a Dll&amp;rsquo;s executing code on an application&amp;rsquo;s behalf, the Dll can NEVER call CoInitalizeEx on the application&amp;rsquo;s thread. Why? Because you can&amp;rsquo;t know the application&amp;rsquo;s threading model, so you can&amp;rsquo;t get it right. If</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Things you shouldn't do, part 2: Dll's can't ever call CoInitialize* on the application's thread.</title><link>http://blogs.msdn.com/larryosterman/archive/2004/05/12/130541.aspx#130626</link><pubDate>Wed, 12 May 2004 18:16:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:130626</guid><dc:creator>Junfeng Zhang</dc:creator><description>The not so great news is PostQueuedCompletionStatus is NT only. QueueUserAPC is available in 9x though. </description></item><item><title>re: Things you shouldn't do, part 2: Dll's can't ever call CoInitialize* on the application's thread.</title><link>http://blogs.msdn.com/larryosterman/archive/2004/05/12/130541.aspx#130829</link><pubDate>Thu, 13 May 2004 00:28:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:130829</guid><dc:creator>Catatonic</dc:creator><description>Great article. I recently came across a DLL that called CoInitialize, and this caused my DLL (a COM component) to fail. Luckily I had the source code to this DLL. I'm not sure what could be done without the source.</description></item><item><title>re: Things you shouldn't do, part 2: Dll's can't ever call CoInitialize* on the application's thread.</title><link>http://blogs.msdn.com/larryosterman/archive/2004/05/12/130541.aspx#130893</link><pubDate>Thu, 13 May 2004 02:36:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:130893</guid><dc:creator>Larry Osterman</dc:creator><description>Yech.  Please tell me that that DLL wasn't part of a shipping system :).&lt;br&gt;&lt;br&gt;And if it was, that it wasn't from a Microsoft product :)&lt;br&gt;</description></item><item><title>re: Things you shouldn't do, part 2: Dll's can't ever call CoInitialize* on the application's thread.</title><link>http://blogs.msdn.com/larryosterman/archive/2004/05/12/130541.aspx#131033</link><pubDate>Thu, 13 May 2004 10:09:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:131033</guid><dc:creator>Catatonic</dc:creator><description>Definitely not a shipping system. The DLL was a project from CodeProject.com. So basically it was sample code. It did work perfectly apart from the CoInit/UnInit though.</description></item><item><title>re: Things you shouldn't do, part 2: Dll's can't ever call CoInitialize* on the application's thread.</title><link>http://blogs.msdn.com/larryosterman/archive/2004/05/12/130541.aspx#131123</link><pubDate>Thu, 13 May 2004 14:12:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:131123</guid><dc:creator>Larry Osterman</dc:creator><description>That's a relief.  Now the problem is: How do you fix it?  Any clients that successfully use this module depend on it's calling CoInitialize/CoUninitialize.  'Tis a puzzlement.&lt;br&gt;&lt;br&gt;In your case you can just rename your private version of the DLL.  But what if it had shipped?&lt;br&gt;</description></item><item><title>re: Don't use vbscript/jscript to write your custom actions!</title><link>http://blogs.msdn.com/larryosterman/archive/2004/05/12/130541.aspx#381354</link><pubDate>Mon, 28 Feb 2005 03:38:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:381354</guid><dc:creator>Aaron Stebner's WebLog</dc:creator><description /></item><item><title>Serious bug in .NET framework 2.0 - IShellLink interface crashes - Page 2 | keyongtech</title><link>http://blogs.msdn.com/larryosterman/archive/2004/05/12/130541.aspx#9362305</link><pubDate>Thu, 22 Jan 2009 06:51:33 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9362305</guid><dc:creator>Serious bug in .NET framework 2.0 - IShellLink interface crashes - Page 2 | keyongtech</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.keyongtech.com/428983-serious-bug-in-net-framework/2"&gt;http://www.keyongtech.com/428983-serious-bug-in-net-framework/2&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>