Migrating shared assemblies to GAC - Best Practises? - 03-05-2006 , 05:31 PM
We've got 2 assemblies that's been used for the last 6 months (with slight
updates now and then) for common use amongst the teams applications.
It's now time for these assemblies to be migrated to the GAC for all new
created apps. It's classnames is registered in the web.config file. It has
been deciced that the class name registrations and configurations will be
added to the machine config on the staging and production machines.
Is there any best practise on how to migrate these files to the GAC? The
problem is that we *don't* want the old applications which have registered
the assemblies in the web.config to pick up the settings within the machine
config. What is the best way to migrate these assemblies to the GAC?
Any advice, or suggestions appreciated.
|Thread Tools||Search this Thread|