Probably not. The software I work on is for helping distilleries stay compliant with TTB reporting rules and regulations. The other stuff we offer is gravy :)

This is a problem I used to run into a lot. I don't know if it's the best way, but the way I always deal with this problem is to put all my 3rd party DLLs (and even internal DLL references) in their own folder structure and include it as part of the solution. I usually just make solution folders for this. When you add references, make sure you reference the files there and not anything out of the GAC. Usually you don't even have to install the 3rd party libraries this way so I think it works pretty well. It also helps deal with version incompatibilities since you know everyone will be using whatever is in TFS and not installed on their machine.

My first programming project was in high school in 1998 or 99 developing a program in VB6 to parse a text file exported from a database which was then used to create student and teacher accounts in a Novell Directory Services tree. You could also use one of the exported files to edit user accounts or delete user accounts. Along with creating accounts, it would create a directory structure and set up permissions for teachers and students where students could submit papers to an inbox and receive graded papers from an outbox. It took me about 3 weeks and I was paid $15/hr, a free hotel stay, and free steak dinners every night. Considering my programming skill then, I can say I was actually probably overpaid... I didn't complain about it though :)