Best way to deploy set of shared .Net assemblies

Posted on 2005-04-27
Last Modified: 2008-01-09
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,
Larkin Young
Question by:larkinyoung
    LVL 18

    Accepted Solution

    keep your shared folder
    and do the following:
    1. change all reference assemblies to assemblies inside shared folder
    2. make sure that "Copy Local" flag is set to true for all assembly references

    close and reopen the solution.

    if developers don't want to update those assemblies yet.... just make sure that they don't  update those shared folder
    LVL 4

    Expert Comment

    You can create a post build Batch file which will be run once ur build is completed

    You simply create a batch file which does to copy task for u and follow the steps below

    1.Right click on a project whose assembly u need to copy and goto Project Properties
    2. GOTO Common Properties/ Build Events
    3. Give ur batch file in "Post-build Event command Line"

    as it is a batch file u can do any thing with it ;)

    Nachiket shah

    Featured Post

    Threat Intelligence Starter Resources

    Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

    Join & Write a Comment

    In order to hide the "ugly" records selectors (triangles) in the rowheaders, here are some suggestions. Microsoft doesn't have a direct method/property to do it. You can only hide the rowheader column. First solution, the easy way The first sol…
    Summary: Persistence is the capability of an application to store the state of objects and recover it when necessary. This article compares the two common types of serialization in aspects of data access, readability, and runtime cost. A ready-to…
    Illustrator's Shape Builder tool will let you combine shapes visually and interactively. This video shows the Mac version, but the tool works the same way in Windows. To follow along with this video, you can draw your own shapes or download the file…
    Here's a very brief overview of the methods PRTG Network Monitor ( offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…

    734 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    25 Experts available now in Live!

    Get 1:1 Help Now