Eric,

Do you use anything like SourceSafe? If so, you can share SourceSafe "projects" among other projects, your DLL would be shared around the various projects that other developers are working on ... basically that way everyone would have access to the exact same file.

~~Bonnie


>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!