tags:

views:

34

answers:

2

I noticed that the DLLs in the bin folder for asp.net websites do not seem to be getting saved. When I goto a new computer and get latest I am missing the DLLs.

What is the correct way to fix this ? Should I create a seperate folder to contains all DLLs ? And then can I somehow tell my bin references to goto that folder to get the DLLs?

+1  A: 

You do not want to check your compiled .dlls in with your source control. If you have other dlls that are not directly compiled by your application then you should create a library folder in your directory structure that contains then, and check that folder in.

Mike C.
Sometimes you have to check in your DLLs. We're in a financial services situation where we need to be able to show what was compiled on a certain date is what was moved to production on a certain date. The only way to do this is to version control the compiled objects as well.
Robaticus
Why is this a bad practice? Its more convient to not have to create another folder for DLLs since the bin folder has them already?
punkouter
+1  A: 

If you are usign third party dlls, you should absolutly consider putting them into tfs...

If those dll comes from antoher projet from the same solution, you should not put them into tfs.

If you use a base class library in multiple solution, i would consider usign the build functionality that tfs offers. You can them acces your lastest build from a network share (adding a this shared as a trusted source) or directly access those dll from tfs source control.

EDIT: you can always go back in time in tfs without having to save whats compiled....

Developer IT