<?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>Script In IE Security Part Six: Creating Objects With State</title><link>http://blogs.msdn.com/b/ericlippert/archive/2004/01/21/61236.aspx</link><description>Ideally the call to QueryCustomPolicy would take an argument representing the moniker for the persisted state so that this could be taken into account when the Security Manager made its decision whether or not to allow the persisted state to load. Unfortunately</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>.NET 2.0 ActiveX Control Gotchas (Safe for Scripting and Hooking into Events)</title><link>http://blogs.msdn.com/b/ericlippert/archive/2004/01/21/61236.aspx#9692234</link><pubDate>Wed, 03 Jun 2009 22:24:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9692234</guid><dc:creator>Rick Minerich's Development Wonderland</dc:creator><description>&lt;p&gt;I’ve recently been building an ActiveX Control in .NET 2.0 and thought I would share some of the problems&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9692234" width="1" height="1"&gt;</description></item></channel></rss>