In c# project, Is AppDomain frequently used ?

Question

4.00/5 (1 vote)

See more:

Recently, I've learned about AppDomain, But I can't understand how to use it in the real project.
Is the Default AppDomain not enough for one process?
In which case, creating a new AppDomain is more suitable?
Hope someone can solve my question. Thank you!!!!

Posted 10-May-14 22:04pm

apthskyi

Add a Solution

2 solutions

Solution 2

IMO, as far as possible, let the framework manager your application domains.

Posted 10-May-14 22:40pm

Abhinav S

Comments

Kornfeld Eliyahu Peter 11-May-14 4:45am

Let me not to agree with you! Once I wrote a tip about how to host multiple WCF services under the same Windows Service. It came from a real project and it uses Application Domain to isolate the WCF services - the framework was not handle it alone and that could be a disaster...

apthskyi 11-May-14 21:03pm

Hi Peter,
Do you create a new AppDomain for each WCF Service?

Kornfeld Eliyahu Peter 12-May-14 2:19am

I load every dll (that represent one WCF service) into a different AppDomain, that way if one of the services crashes the whole business still runs...

apthskyi 12-May-14 20:51pm

Nice design~

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)

OriginalGriff · Accepted Answer · 2014-05-10T22:15:00

I don't personally use AppDomains, but then - I don't interface with tasks that are liable to fail: I prefer to write ones that don't by using defensive programming techniques.

If you look at the MSDN documentation: http://msdn.microsoft.com/en-gb/library/system.appdomain.aspx[^] it's pretty clearly stated:

Application domains, which are represented by AppDomain objects, help provide isolation, unloading, and security boundaries for executing managed code.

Use application domains to isolate tasks that might bring down a process. If the state of the AppDomain that's executing a task becomes unstable, the AppDomain can be unloaded without affecting the process. This is important when a process must run for long periods without restarting. You can also use application domains to isolate tasks that should not share data.

If an assembly is loaded into the default application domain, it cannot be unloaded from memory while the process is running. However, if you open a second application domain to load and execute the assembly, the assembly is unloaded when that application domain is unloaded. Use this technique to minimize the working set of long-running processes that occasionally use large DLLs.

Covers it pretty well, I think.