<?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>Coding with Security Policy in .NET 4 part 2 – Explicit uses of CAS policy</title><link>http://blogs.msdn.com/shawnfa/archive/2009/06/09/coding-with-security-policy-in-net-4-part-2-explicit-uses-of-cas-policy.aspx</link><description>Over the last few posts, I’ve been looking at how the update to the CLR v4 security policy interacts with how you write managed code against the v4 .NET Framework.&amp;#160; So far we’ve looked at the implicit uses of CAS policy, such as loading assemblies</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Dew Drop - June 10, 2009 | Alvin Ashcraft's Morning Dew</title><link>http://blogs.msdn.com/shawnfa/archive/2009/06/09/coding-with-security-policy-in-net-4-part-2-explicit-uses-of-cas-policy.aspx#9724049</link><pubDate>Wed, 10 Jun 2009 15:18:33 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9724049</guid><dc:creator>Dew Drop - June 10, 2009 | Alvin Ashcraft's Morning Dew</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.alvinashcraft.com/2009/06/10/dew-drop-june-10-2009/"&gt;http://www.alvinashcraft.com/2009/06/10/dew-drop-june-10-2009/&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>