When deploying .Net Serviced Components on W2K, the dllhost surrogate process is the only option for hosting out of proc components.
So if: 1. You're running on W2K. 2. You need to use Serviced components. 3. You want to host them out-of-process or the client is not a COM+ server application. You have to GAC them so that the assembly resolver can find them. The GAC places versioning constraints on all installed components which is good and bad. I believe that for sharing components there is a way to define assembly binding probing path explictly via the machine.config but this option sounds like it requires a bit too much customization to be a decent solution. Yes/No? Question: Is there a way to host Serviced components without being forced into GAC deployment and versioning? I've gotton the impression from some posts that Win2003/COM 1.5 might allow me to host multiple sharable components without having the versioning applied by GAC deployment. However, based on the information I've found so far, no COM 1.5 features appear to support this. I'm trying to find some detailed info on Serviced component hosting on Windows Server 2003/COM 1.5. Specifically, I'm trying to find out how/if it's possible to deploy/host multiple interdependent Serviced components in a non-GAC'd deployment. Can someone confirm or deny this or point me in the right direction to find the answer? =================================== 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 CSharp August 30 - September 3, in Los Angeles http://www.develop.com/courses/edotnet View archives and manage your subscription(s) at http://discuss.develop.com
