<?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>Using the MMC Snap-In to Configure 64 Bit CAS Policy</title><link>http://blogs.msdn.com/shawnfa/archive/2007/03/15/using-the-mmc-snap-in-to-configure-64-bit-cas-policy.aspx</link><description>The .NET Framework SDK ships with a MMC Snap-In which enables you to, among other things, avoid using caspol to modify your local security policy. Since each runtime installed on your machine has independent security policy , the MMC Snap-In will only</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Using the MMC Snap-In to Configure 64 Bit CAS Policy</title><link>http://blogs.msdn.com/shawnfa/archive/2007/03/15/using-the-mmc-snap-in-to-configure-64-bit-cas-policy.aspx#2947312</link><pubDate>Mon, 28 May 2007 18:32:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2947312</guid><dc:creator>AndreaOctet</dc:creator><description>&lt;p&gt;This stuff is a nightmare. MS couldn't make it more complex...&lt;/p&gt;
</description></item></channel></rss>