My previous post is begging the question "so what is the SSCLI's zone mapping policy?" It's actually quite simple, the source for SecurityPolicy::QuickGetZone in clr\src\vm\securitypolicy.cpp shows that SSCLI maps a URL to: NoZone if the URL is NULL MyComputer if the URL is a file URL Internet for all other cases
Similar Posts
On the topic of zones and the CLR ... Windows lets you define custom zones outside of the standard ones that the CLR knows about (see MSDN's topic on Security
Before digging into a pretty clever optimization that the SSCLI makes for certain special permission demands, I want to point out that everything I'm about
We've looked at how the CLR supports mapping a custom zone to the Internet zone and how you can modify the SSCLI to handle whatever zone mapping policy
One of my most read blog posts (and one of the reasons I created this blog in the first place -- to answer what was one of the most asked questions on
