For W2K it's GAC all the time. There are some workarounds, but any of those require reaching so far into the guts of Enterprise Services that you don't really want to have them running in production.
Windows Server 2003 is your platform. That's where it's all really nicely integrated. I know that this is a platitude, but one should pick the appropriate platform for a business solution and not do it the other way around. The compromises you need to make on W2K vs. Win03 and the additional dev cost you incur may be very well worth the cost of upgrading (including the upgrade cost in Ops). -cv -----Original Message----- From: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Bill Bassler Sent: Friday, June 04, 2004 1:26 PM To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] Best Practices: Sharing business assemblies, the GAC, deployment and component versioning Yes. Unfortunely we're still on W2K here and I believe require dllhost for out of proc components. So is the following correct. If: 1. You're running on W2K. 1. You need to use Serviced components. 2. You want to run them out-of-process. You have to GAC them. Is this correct or do other options? MS has got a real mess with the Component Services "integration" and .Net. =================================== This list is hosted by DevelopMentor(r) http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
