Software Technologies

The answer is yes.

When creating a web project in Visual Studio .NET 2005, the bin folder gets exposed to TFS source control.

Normally, the bin folder is how the web project keeps track of the project references. When a project reference is added to the project, the .dll is copied to the bin directory.

In a source controlled environment, this copy is "noticed" by Visual Studio 2005 and exposed to the source control process. This means that you can check in all the .dlls added to the bin folder.



The Bin folder is not visible on the Source Control Window. So, when you checked in the .dll files, the files will be drop on the drop release folder.

I don't see why we need to put bin folder into our source control. It is not a wise idea bro. If you want to put your dll, let say external dll or third party library such as nhibernate.dll or P&P EntLib dlls, put it in another folder other than bin, obj, debug..etc..if you 're developing multitier apps or seperate your module into several projects, it is much easier because you can just Add Reference to you projects instead of refer to dll.
In our development team here, we organise all our tools, and libraries properly, put it into the right folder.Example: put all the externall dlls into a folder named 'Library'. When new developer join our team. they can just get latest the root folder, then he can compile the solution without any problem.