Hey Bill -- I'm not sure if you are talking to me or the previous poster. I thought my answer addressed your questions, in particular the points about best practices, how to avoid deploying private copies of components, how to have each version of the clients reference their own versions of the components in a shared environment and your additional question of "Is there a way to tell a client to bind to the assembly with highest build number in the GAC and not to a specific version." Specifically, we do that with publisher policy files. I can elaborate more if it's not clear or maybe we are talking at different levels... Not sure, but willing to try and help...
-----Original Message----- From: Bill Bassler [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 02, 2004 2:00 PM To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] Best Practices: Sharing business assemblies, the GAC, deployment and component versioning Please actually read what was posted and my question. It's OBVIOUS that you didn't. =================================== 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
