Mubbasher Mukhtar | Sharing Development Experience

Providing Host Evidence from an assembly : Evidence is the information that the runtime gathers about an assembly to determine which code group the assembly belongs to. The Code group intern determines the privileges for the assembly. Common forms of evidence are folder, web site, and digital signature. System.Security.Policy. Evidence can be provided to one of the overloads of ExecuteAssembly method. Evidence requires two object arrays at the time of creation. One is array of host evidence , second is array of assembly evidence . Both can be null as well. Zone information can also be used to easily control permissions. Using System.Security; Using System.Security.Policy; Object[] hostEvi = { new Zone(SecurityZone.InternetZone) }; Evidence iEvendence = new Evidence (hostEvi, null); AppDomain mDomain = AppDomain.CreateDomain(“M”); mDomain.ExecuteAssembly(“SecondAssembly.exe” , IEevedence); To provide hostEvidence to Application domain: Ap...

Creating Application Domains: Application domain is just like process, provides separate memory space, and isolates from other code. But it’s quite light weight. It also provides the following advantages: 1-       Reliability : If a domain crashes, it can be unloaded. Hence doesn’t affect the other assemblies. 2-       Efficiency : Loading all assemblies in one domain can be cumbersome and can make the process heavy but Appdomains are efficient in this manner. Important properties of AppDomain: ApplicationIdentity , ApplicationTrust , BaseDirectory , CurrentDomain , DomainManager , DomainDirectory , Evidence , FriendlyName , ID , RelativeSearchPath , SetupInformation , ShadowCopyFiles . Important methods of AppDomain: ApplyPolicy , CreateCOMInstanceFrom , CreateDomain , CreateInstance (Assembly). To create an AppDomain: AppDomain adomain = AppDomain.CreateDomain(“D”); To execute an assembly:...