Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / CLR / March 2006

Tip: Looking for answers? Try searching our database.

Using Appdomains on the client

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
John Grant - 17 Mar 2006 02:48 GMT
I was thinking of using appdomains and loading a winform assembly in each
one.  This would be a client application.  Creating an appdomain seams
lighter than a process and I can share data between appdomains.  Any reason
why I shouldn’t?  Any examples?  I can create an appdomain and execute an
assembly in that domain on a seperate thread, but if an exception occurs I
don't know what domain that app was running in.


-John
Pandurang Nayak - 24 Mar 2006 20:45 GMT
Nothing wrong. But depends on the situation. Remember that multiple
appdomains does not mean multiple processes - so the following applies:
- If an appdomain crashed the process, all other appdomains are crashed too
(no process-level isolation)
- Each appdomain that is created is still in the same process - and hence
from the perspective of the processor, still being considered as a single
process. This means that if you had too many appdomains, your execution might
take longer.

But sure, there are many advantages of creating an appdomain on-the-fly -
which is why I think it is there :)  

Regards
Pandurang

Signature

blog: www.thinkingMS.com/pandurang

> I was thinking of using appdomains and loading a winform assembly in each
> one.  This would be a client application.  Creating an appdomain seams
[quoted text clipped - 5 lines]
>
> -John
Naveen - 25 Mar 2006 01:56 GMT
Do you have any particular requirement to load assemblies in different
appdomains?
Appdomains are primarily used to running partially trusted code or
unload assemblies (because assemblies cannot be unloaded so the
appdomain in which it is loaded is unloaded). If you have any of these
requirements then it may be a good choice to use appdomains. Keep in
mind appdomains are lightweight process and they also have additional
over heads.

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.