<?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.0 – Implicit uses of CAS policy</title><link>http://blogs.msdn.com/shawnfa/archive/2009/05/27/coding-with-security-policy-in-net-4-0-implicit-uses-of-cas-policy.aspx</link><description>Last week we looked at sandboxing and the v4 CLR – with the key change being that the CLR now defers exclusively to the host application when setting up sandboxed domains by moving away from the old CAS policy model, and moving instead to simple sandboxed</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>  .NET Security Blog : Coding with Security Policy in .NET 4.0 &amp;#8230;</title><link>http://blogs.msdn.com/shawnfa/archive/2009/05/27/coding-with-security-policy-in-net-4-0-implicit-uses-of-cas-policy.aspx#9647487</link><pubDate>Thu, 28 May 2009 18:35:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9647487</guid><dc:creator>  .NET Security Blog : Coding with Security Policy in .NET 4.0 &amp;#8230;</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.tscmpro.com/?p=3775"&gt;http://www.tscmpro.com/?p=3775&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>More Implicit Uses of CAS Policy: loadFromRemoteSources</title><link>http://blogs.msdn.com/shawnfa/archive/2009/05/27/coding-with-security-policy-in-net-4-0-implicit-uses-of-cas-policy.aspx#9709117</link><pubDate>Mon, 08 Jun 2009 21:59:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9709117</guid><dc:creator>.NET Security Blog</dc:creator><description>&lt;p&gt;In my last post about changes to the CLR v4 security policy model, I looked at APIs which implicitly&lt;/p&gt;
</description></item><item><title>Temporarily re-enabling CAS policy during migration</title><link>http://blogs.msdn.com/shawnfa/archive/2009/05/27/coding-with-security-policy-in-net-4-0-implicit-uses-of-cas-policy.aspx#9737040</link><pubDate>Fri, 12 Jun 2009 21:27:16 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9737040</guid><dc:creator>.NET Security Blog</dc:creator><description>&lt;p&gt;Over the last few weeks we’ve been looking at the changes to security policy in .NET 4, namely that security&lt;/p&gt;
</description></item><item><title>CLR v4 Security Policy Roundup</title><link>http://blogs.msdn.com/shawnfa/archive/2009/05/27/coding-with-security-policy-in-net-4-0-implicit-uses-of-cas-policy.aspx#9737145</link><pubDate>Fri, 12 Jun 2009 21:34:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9737145</guid><dc:creator>.NET Security Blog</dc:creator><description>&lt;p&gt;Over the last few weeks we’ve been taking a look at the updates to the CLR security policy system in&lt;/p&gt;
</description></item></channel></rss>