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 run them out-of-process. You have to GAC them. (I believe there is a way to define assembly binding definitions via machine.config for sharing components but this option sounds pretty unconsiderable for production apps) Question: 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 to deploy/hosting multiple interdependent Serviced components in a non-GAC'd deployment. I've heard this is possible. If it is, can someone point me in the right direction? =================================== 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
