Creating new AppDomains...how many is too many???

Hi,

I need to create seperate AppDomains to dynamically load assemblies.
But...how many AppDomains is too many?

Is it ok to create 100? Is 1000 too many???
I am trying to work out what the overhead would be if my client app created 100 new AppDomains, one for each dynamic assembly.

Cheers,

Wojka

hey,
i try to google it but there is no luck, if you got answer i will be happy for sharing it...:)

For a 24/7 running service mining data of a pharmacy-system, sending it to the "head quarter" I ran into a bug in the .Net framework where, on some systems the service had a memoryleak. Doing the sending (with WCF) in a separate appdomain for each message. This means the services create about 3.000 appdomains per day, giving a overhead of 30 seconds processortime per day.
According to this link from MSDN running a lot at the same time time isn't gonna be a problem

need to be tested, i think