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

I would write a little back file the regsiters the DLL into the gac with gacutil. I think that also copies it to the GAC folder.
>
>1) Is there going to be multiple versions of this DLL floating around and what is the best way to handle that situation?

The GAC supports multiple versions of a dll. Your ap will use whichever version it was built with, or you can change the config to specify a certain version.

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

Sure, won't hurt. If it is already in the GAC no harm, no foul.

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

BOb