I just had our main eventing service crash. It is a .Net Service written in C#, all of it is managed code. Upon attaching a debugger to the service process and looking at the threads I noticed one of them had System.Winforms calls on it. There are no references whatsoever in the service to Winforms. After further investigation I realized that it was one of our other apps which is launched from the start menu. Apparently the framework is creating an AppDomain for the WinForms application inside the process of the service!!! I realize that it is nifty to have multiple AppDomains in the same process, and I think this is reasonable for regular applications. However, this service is a critical component and we cannot afford to have it crash due to a runaway pointer in another .Net App which is not 100% managed code. How can I ensure that other AppDomains are not loaded into the service process.
I hope I sound composed, because this is really freaking me out. OS on test box that crashed was Windows 2000 Server. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: Essential .NET: building applications and components with C# November 29 - December 3, in Los Angeles http://www.develop.com/courses/edotnet View archives and manage your subscription(s) at http://discuss.develop.com
