Has anybody successfully mixed app domains and UIs? We have an app that has plug-ins (just one at a time), which we'd like to run in a separate app domain (in order to unload, so as to avoid type identity collisions; not for security reasons). The plugins don't themselves contain UI code, but there's a very large & rich interface between part of the app's UI and the plugin.
So, if the UI is in the main app domain, then there's a mountain of stuff to marshal back and forth. On the other hand, if the UI is in the separate app domain, along with the plugin, then we have part of the UI in the main domain, and part in the separate app domain. From what I can tell, both WinForms and WPF don't allow parent and children to be separated by an app domain boundary. Seems like I can do this if the two parts of the UI are different top-level windows, or if I create the parent-child relationship at the window handle level, but I have no idea what the consequences of this might be. Any ideas? Visual Studio manages this somehow when it allows you to design with components in the same solution and use type editors!? Kevin =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
