Difference between AppDomain and Process in .net

Question

0.00/5 (No votes)

See more:

.NET3.5

Hi,

Can anyone brief me the differences between the Appdomain and Process in .net.Also,please tell me why are Appdoamins usefull.

Regards
Chaithanya M

Posted 2-May-11 1:13am

M.CHAITHANYA

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2011-05-02T03:16:00

One aspect is extremely important:

Application Domain is useful when you need to unload loaded assembly. This is not allowed by .NET due to safety purpose: what is some code will be called after unloading?

If you try to create re-loadable plug-ins, it will create a string memory leak. If you want to load a different version of the plug-in during run-time, old version will stay in memory. The only way is this: load (or compile into memory which effectively performs compile-and-load) a reloadable assembly in a separate Application Domain and used it through this domain. As the the domains are memory-isolated as strongly as processes, there is no any danger in unloading the domains, so there is an unload method of the Application Domain, with all the assemblies loaded in it.

Please see my past solution describing skeletons of architecture using this feature:
Create WPF Application that uses Reloadable Plugins...[^],
AppDomain refuses to load an assembly[^],
code generating using CodeDom[^].

—SA

jim lahey · Answer 2 · 2011-05-02T01:46:00

Solution 1

First link in google when I search for "difference between AppDomain and Process":

http://www.dotnetspider.com/forum/ViewForum.aspx?ForumId=139934[^]

Posted 2-May-11 1:46am

jim lahey

Afazal MD 3104209 · Answer 3 · 2013-09-18T22:16:00

What is AppDomain?
Each application running within a process, AppDomain is also a light-weight process or we can say logical unit which having group of assemblies (this is a container which contain group of assemblies ) and this exist inside of the process at isolation level of same process, this allows to run multiple assemblies within same process and prevent them for direct access.

Running Dot Net Application Within AppDomain:
Once any dot net application run, Operation system shell load CLR into a process and new AppDomain been created in the same process and load all the assemblies in the created AppDomain, now from the AppDomain code will get executed.

When to Create Custom AppDomain:
We can create own AppDomain, now the thing is in which scenario we can create own AppDomain. Suppose run time we need to add or remove the assemblies without interruption the running application then we can create own AppDomain.

Thanks
mdafazal@gmail.com

Difference between AppDomain and Process in .net

3 solutions

Solution 2

Solution 1

Solution 3

Add your solution here

Preview 0