@Aaronontheweb one of my coworkers just showed me some AppDomain stuff. For the multinode tests wouldn't it be easier to load the child nodes up in their own app domain? It would allow us to attach a debugger alot easier
@annymsMthd you can use the Child Process Debugger in Visual Studio to do the same thing
but the guy you should talk to about redoing the MultiNodeTestRunner is @smalldave
let me get you the download link for the multi-node test runner
to answer your question though, I don't know what the downsides would be of using an AppDomain - part of me think it's a better idea to leave this stuff as-is and let each node have its own independent process-level resources
but don't all .NET processes share the same threadpool anyway?
i.e. isn't the CLR threadpool a shared resource across all of them? or is that not right?