>I believe you misunderstood what I was trying to convey. Let’s say I make a DLL for my fellow coworkers and myself to use. What is the best way to give them this DLL so that they can use it? Is the best way to just give them the DLL or should I write up an installer that will install in into the GAC for them? Can they even reference a DLL that is installed in the GAC or do they need to have the file separate of the GAC and stored in some folder? My concerns are as follows:
>
>1) Is there going to be multiple versions of this DLL floating around and what is the best way to handle that situation?
>2) When they deploy their application they will be deploying the DLL as well. Is it best for me then to write a MSM installer module for them to use? If so, then I would be giving them the DLL as a separate file as well as the MSM file, correct?
>
>I would like know what people are doing currently when they give other developers their DLL's/components to use in their applications. Thanks again for your help!

Eric;

We are discussing how we will do this. Some concerns are who has the source code and who can modify it? There are many ways that this can be done but we are attempting to determine the good and bad points before we get too deep into this subject.

A suggestion from one of our developers is to use VSS to maintain version control. Make it available to the original developer (this can include additional developers in another scenario) and use MTS to deploy the component. Again, we have a lot of work to do before we will be satisfied with any scheme.

At our workplace we have many developers and two main departments. We have what I term a “cubical mentality”, in more ways than one. We think inside the cubical and nothing filters out of our specific areas.

To make best use of OOP we have to communicate and plan how to create, use and deploy components in .NET. Either a few of us will cooperate and benefit or we will just go back to our little worlds to reinvent the wheel over and over. Somehow I do not expect the whole corporation to follow what we are attempting to do.

Additionally, we are going to have an on line application that will define each component available, what it does, where it is located, parameters, creator, version, etc.

Tom