I vote not to install to GAC. I generally avoid the GAC if I can. To joe, the original poster, you might be surprised that I actually saved the developers in my team a lot of time by not battling with GAC references.
Originally we had to ask developers to install log4net, NUnit, Infragistics, and so on and so on in the GAC, before our solution can even compile. And then somebody would have an incorrect version, solution would fail in his/her machine, other developers would try to help out... lost time. The solution was to create binary dll references to these tools from a standard thirdparty folder. This folder is also checked in sourcecontrol. And in Visual Studio, you can add the dlls as "Solution Items". This means that on a fresh machine (well at least VS+addins and source control client is installed!), all the developer had to do was "Open solution from source control", and it would bring all the projects including the binaries of nunit log4net etc. Click Re-build solution, job done. Developers can work with out installing anything.
