Yes. As far as I understand the workings of binding redirects and publisher policies you are correct. There wasn't really an objection to GACing components per se. But being limited to that option is, well ... limiting. I think that we can all agree that using binding redirects and publisher policies adds a level of complexity that certain projects might not need. Should the fact that one decides that they require the use of Enterprise Services force them into build-level versioning for their modules? It would seem that its more a question of the technical limitations of a particular version of Enterprise Services and the OS. Is this more or less the case or am I way off base?
=================================== 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
