Best way to deploy set of shared .Net assemblies
Posted on 2005-04-27
This may not be the correct topic area, but I will give it a shot. The situation I am in is that the project team I am working on uses Rational ClearCase for source control (if you hate VSS, don't every try ClearCase ;-)). The frustrating issue that keeps popping up is that there are several assemblies whose projects are not included in the main solution (custom controls, etc) but that are updated every so often. With ClearCase, you cannot add assemblies to the source control because for whatever reason Visual Studio wants to have write access to the assemblies even if they aren't being rebuilt (which is annoying, btw) so any time I update the source code and rebuild these "helper" assemblies, I have to copy the assemblies to a shared folder under source control that is outside the application's bin folder so the other developers can copy the updaetd assembly into their own local application bin folder (we do independent testing on our individual virtual dev environments). Is there a convenient way, using either a deployment project, or some technique utilizing assembly redirection/codebase configuration to simplify or automate this process? I cannot seem to figure out a way to create a setup project that will just install the assembly to the GAC, and not try to install the assembly to a local folder. Any suggestion swould be greatly appreciated--I am experienced with .Net but I have honestly not done any advanced tasks with setup/deployment projects.
Thanks in advance,