Hi all, Uh'memba back in the day.... not too terribly long ago.... ;-) When we created COM objects in local servers that registered the class object using REGCLS_SINGLEUSE so that each instance of the objects we were asking for ran in their own process space?
How does one create a .NET object in a separate process? Keep in mind, this is different than the standard CAO and SAO remoting structure. If I register a CAO, it always runs in the process space of the registering process. That is not acceptable for what I need. Currently, I have the code that must execute in a separate process all in native C++ code that is initiated in it's own process using CreateProcess from a DLL used in the managed world through interop. However, it just seems that there must be a more elegant way to do this in more of a "pure" .NET way. Am I missing something? Does not seem that Activator will do it for me. I cannot seem to find a facility in the framework to allow me to specify that a specific object in a specific assembly must be created in a new process, even if the target object lives in an exe. It does not appear that I can create a new AppDomain in a NEW process, unless I am missing something. ExecuteAssembly does not do the trick. Thanks! -T
