<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Determining the Security Rules for Your Assemblies &#8211; #14</title>
	<atom:link href="http://blogs.rev-net.com/ddewinter/2009/06/03/determining-the-security-rules-for-your-assemblies/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.rev-net.com/ddewinter/2009/06/03/determining-the-security-rules-for-your-assemblies/</link>
	<description>A Developer's Melting Pot: LINQ to SQL, Entity Framework, .NET Security...</description>
	<lastBuildDate>Sat, 03 Jul 2010 01:28:31 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: David DeWinter</title>
		<link>http://blogs.rev-net.com/ddewinter/2009/06/03/determining-the-security-rules-for-your-assemblies/comment-page-1/#comment-13143</link>
		<dc:creator>David DeWinter</dc:creator>
		<pubDate>Thu, 26 Nov 2009 04:55:30 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rev-net.com/ddewinter/2009/06/03/determining-the-security-rules-for-your-assemblies/#comment-13143</guid>
		<description>Good call, Jamebo. I&#039;ll update the flowchart when I find the Visio document. (I think it&#039;s still on my work computer.)

By &quot;all other code is transparent,&quot; MSDN means overridden virtual methods and interface implementations, assuming those virtual methods and interfaces were defined in another assembly. The method must maintain the same transparency it did in the original assembly.</description>
		<content:encoded><![CDATA[<p>Good call, Jamebo. I&#8217;ll update the flowchart when I find the Visio document. (I think it&#8217;s still on my work computer.)</p>
<p>By &#8220;all other code is transparent,&#8221; MSDN means overridden virtual methods and interface implementations, assuming those virtual methods and interfaces were defined in another assembly. The method must maintain the same transparency it did in the original assembly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamebo</title>
		<link>http://blogs.rev-net.com/ddewinter/2009/06/03/determining-the-security-rules-for-your-assemblies/comment-page-1/#comment-11857</link>
		<dc:creator>Jamebo</dc:creator>
		<pubDate>Thu, 05 Nov 2009 10:02:11 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.rev-net.com/ddewinter/2009/06/03/determining-the-security-rules-for-your-assemblies/#comment-11857</guid>
		<description>I tested this case:
Assembly Full Trusted + Level 2 + SecurityCritical Attribute  + APTCA. The assembly should be Full Critical.
But in your flow chart, it is transparent.

In MSDN, it said:
SecurityCritical with Level 2:  All code that is introduced by types in this assembly is critical; all other code is transparent. 

It seems all types and members are full critical. How to understand &quot;all other code is transparent.&quot;?
What the &quot;all other code&quot; means?

Thanks
-Jamebo</description>
		<content:encoded><![CDATA[<p>I tested this case:<br />
Assembly Full Trusted + Level 2 + SecurityCritical Attribute  + APTCA. The assembly should be Full Critical.<br />
But in your flow chart, it is transparent.</p>
<p>In MSDN, it said:<br />
SecurityCritical with Level 2:  All code that is introduced by types in this assembly is critical; all other code is transparent. </p>
<p>It seems all types and members are full critical. How to understand &#8220;all other code is transparent.&#8221;?<br />
What the &#8220;all other code&#8221; means?</p>
<p>Thanks<br />
-Jamebo</p>
]]></content:encoded>
	</item>
</channel>
</rss>
