Hello, My team has developed an application that uses Multiple AppDomains and Multiple UI threads to house somewhat related components (or sub-applications) within a common UI "shell" allowing these components to communicate in a loosely coupled fashion and all that other good stuff (its somewhat CAB like, but we think better). It works great, except we are running into a problem with the vs2003 debugger where we set a break point in one of the sub-applications and then close the sub-app (which causes an Application.Exit in its AppDomain) and then re-open the sub-app (which creates a new AppDomain and UI Thread). Soon after doing that, when the break point is hit, the debugger will freeze for 10 seconds and then throw a first chance ThreadStopException which will cause the sub-app to crash. The problem only seems to happen in the debugger and under very limited testing in vs2005, we don't see the problem (unfortunately we are still stuck in a 1.1 world for now).
Has anyone tried anything similar or seen this behavior from the debugger? I googled for ThreadStopException and found some chatter about the Watch window causing this, but we still get this problem even if we hide all the watch/locals/etc windows. Thanks in advance for any suggestions. Mike =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
