Shulou(Shulou.com)06/02 Report--

Editor to share with you about the C# application domain, I believe that most people do not know much about it, so share this article for your reference, I hope you can learn a lot after reading this article, let's learn about it!

In the previous traditional development, we all know that an application corresponds to a process, and the virtual memory is assigned to the process, and the actual physical memory is mapped by the operating system, which effectively maintains the security between processes. On the other hand, each process consumes a certain amount of system resources, which reduces the performance, and the communication between processes is also troublesome.

A new concept has been introduced in .NET: C # application domain (AppDomain). It can be understood that many application domains can run in the same .NET process, which can reduce system consumption, while different domains are isolated from each other and are guaranteed in terms of security. In addition, it is relatively simple to communicate between different domains within the same process.

Application domains involve a lot of content, and this article briefly describes the following two aspects:

1. How to create and unload domains

2. How to realize the communication between domains

How to create and unload domains

The AppDomain class is provided in .NET to provide isolation, uninstallation, and security boundaries for executing managed code.

AppDomainSetup info = new AppDomainSetup (); info.LoaderOptimization = LoaderOptimization.SingleDomain; AppDomain domain = AppDomain.CreateDomain ("MyDomain", null, info); domain.ExecuteAssembly ("C:\\ test\\ DomainCom.exe"); AppDomain.Unload (domain)

1. Use the AppDomainSetup class to define the properties of the new domain. For example, you can set the root directory of the application and set the category of the loaded program.

In the example, SingleDomain is used to indicate that the loader must not share internal resources between C # application domains, and other properties such as MultiDomain, MultiDomainHost, and so on can be used.

2. Create a new domain named MyDomain on the fourth line

3. Execute an application inside the new domain on line 5

4. Line 6 uninstalls the new domain

After being created in this way, even if a system exception occurs in the execution of the new domain, it will not affect the execution of the original domain, so you can do programs like WatchDog (monitor subroutine, restart once you exit).

Second, how to realize inter-domain communication

The common language runtime prohibits direct calls between objects in different domains, but we can copy these objects or access them through proxies

AppDomainSetupinfo2=newAppDomainSetup ()

Info2.LoaderOptimization=LoaderOptimization.SingleDomain

Info2.ApplicationBase= "C:\\ test"

AppDomainAppDomaindomain2=AppDomain.CreateDomain ("MyDomain2", null,info2)

ObjectHandleobjHandle=domain2.CreateInstance

("DomainCom", "DomainCom.TestStatic")

ICollectionobj=objHandle.Unwrap () asICollection

Inti=obj.Count

Domain2.ExecuteAssembly ("C:\\ test\\ DomainCom.exe")

AppDomain.Unload (domain2)

The initial code is all the same, focusing on the following aspects:

Line 5 creates an object (class DomainCom.TestStatic) in the new domain and returns a proxy ObjectHandle class for passing objects between multiple C # application domains

DomainCom.TestStatic must inherit from the MarshalByRefObject class, which is simple for demonstration purposes, inheriting from the ICollection interface and implementing a Count property:

UsingSystem; usingSystem.Collections.Generic; usingSystem.Text; usingSystem.Collections; namespaceDomainCom {publicclassTestStatic:MarshalByRefObject,ICollection {get {countcount=count*2; returncount;} unimplemented Code # region unimplemented Code publicboolIsSynchronized {get {thrownewNotImplementedException ();}} publicobjectSyncRoot {get {thrownewNotImplementedException ();}} publicvoidCopyTo (Arrayarray,intindex) {thrownewNotImplementedException ();} publicIEnumeratorGetEnumerator () {thrownewNotImplementedException ();} # endregion}}

2. Line 6 gets the object in the new domain

3. Assign values to objects in the new domain in the seventh in the current domain

Line 8 executes the application in the new domain, in which a dialog box displays the value of Count

The above is all the content of this article "talking about C# Application Domain". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.