Skip to main content

Configuring Applications Domains


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:

AppDomain mD = AppDomain.CreateDomain(“m”, iEvendence);

Configuring Application Domain Properties:
One can provide new Configuration settings for newer AppDomain through Constructors. AppDomain setup is used for this configuration purpose.

 

AppDomain setup properties are:

ActivationArguements, ApplicationBase, ApplicationName, ApplicationTrust, ConfigurationFile, DisallowApplicationBaseProbing, DisallowBindingRedirects, DisallowDownload, DisallowPublisherPolicy, DynamicBase, LicenceFile, LoadOptomization, PrivateBinPath.
 

Labels:

Comments

Post a Comment

Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...
Post a Comment
Continue Reading »

Using ADO.NET Transaction Object, Saving CLR Objects and SqlNotificationRequest

Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : A transaction can’t span multiple connections.   Local and distributed transaction ares supported in 1.x you have to Enterpeise seveices library to regiser multiple connections and then call EnlistDistributedTransaction. Distributed Transaction Coordinator is required for Distributed transaction that’s available on windows 2000 & +. In 2.X and later use TransactionScope object. Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : Dispoase of the transaction must be called to complete the transaction. Distributed Transaction : ...
Continue Reading »

Code Access Security in .Net

Namespace: System.Security What is Code Access Security? Code Access Security is a mechanism through which Developers and administrators can restrict code from accessing different resources , without caring about the users’ access level. You can also control resource that can’t be controlled through traditional RBS (Role Based Security), e.g. Web Requests and DNS requests etc. It can be only applied to Managed Applications. These restriction are applied not to the user instead to the Application, thus it does not require username or password. Evidence: It is the information that runtime gather about the assembly to determine which Code Groups the assembly belongs to. The following table shows the common types of evidence that a host can present to the runtime. Evidence Description Application directory The application's installation directory. Hash Cryptographic hash such as SHA1. Publisher Soft...
Post a Comment
Continue Reading »