Search:   Namespaces Discussions .NET v1.1 Feedback

Significant delay while unloading temporary AppDomain Messages   Related Types This message was discovered on microsoft.public.dotnet.framework.clr. Responses highlighted in red are from those people who are likely to be able to contribute good, authoratitive information to this discussion. They include Microsoft employees, MVP's and others who IMHO contribute well to these kinds of discussions. Post a new message to this list... Steve (VIP) I dynamically load assemblies to discover whether they support certain interface or not. Then I unload this temporary domain by calling AppDomain.Unload method. I don't understand why but this call cause significant delay up to 30 seconds. Can anyone explain why AppDomain.Unload delays execution of the problem for so long. My app is former VC++ 6.0 application migrated to MC++. The class which actually uses this functionality is unmanaged. Does it have something to do with this problem? When I use the same discovery code and unload temporary domain from test console MC++ application everything is OK. Reply to this message...        David Levine When an appdomain is unloaded all the threads with stack in that appdomain must get unwound to the boundary of the appdomain. If unloading the appdomain hangs it might be hung up in a call to an external unmanaged method and it takes that long to time out. What does your code do in the temp appdomain? "Steve" <Click here to reveal e-mail address> wrote in message news:Click here to reveal e-mail address... [Original message clipped] Reply to this message...     System.AppDomain Ad MBR BootFX Best-of-breed application framework for .NET projects, developed by Matthew Baxter-Reynolds and MBR IT

Copyright © Matthew Baxter-Reynolds 2001-2008. '.NET 247 Software Development Services' is a trading style of MBR IT Solutions Ltd. Contact Us - Terms of Use - Privacy Policy - www.dotnet247.com