Originally Posted by
jmcilhinney
A .NET assembly basically looks in the same folder and in the GAC by default for any assemblies it references, so if your developers are adding references to the DLLs you provide and setting Copy Local to True for those references (which should happen by default) then they will end up in the same folder as the EXE and everything will just work.
A slightly better option might be to create a NuGet package and host it on your network. They can then add that package in VS and it will be downloaded from the appropriate source and everything will just work. The nice thing about NuGet is that it makes it easy to package dependencies and also provide updates.