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.