Build always checks out most of 'Bin' directory? (VS2005 Team Suite RC1)

Build always checks out most of 'Bin' directory? (VS2005 Team Suite RC1)

• eddie d

  Jason,
  
  So you are seeing this problem with VSTS 2005 and Visual SourceSafe   Interesting.  How was your solution added to the SourceSafe repository   Was it via Add Solution to Source Control using the Release Candidate IDE
  
  Thanks,
  Ben
  
  

• Florian Struck

  There has been a problem reported with Web Projects and source control in VSTS 2005 where in some circumstances the binaries in the Bin directory end up being checked in (and then checked out on subsequent builds) rather than being excluded from source control as they should be.  Unfortunately, we are having trouble reproducing this behavior in-house.
  
  Is your 'Bin' directory part of a web project
  
  Some of the behavior you describe differs from the other reports about problems with the Bin directory.  For one, I don't believe we've had any other reports about the Bin directory items being checked out on Open.  Also, I haven't heard about the .sln and .vssscc files being checked out in this scenario.
  
  In the case where the .sln and .vssscc files are being checked out, can you do a save all files and run a Compare on those two files to see what changes are being made (if any)
  
  Thanks,
  Ben Ryan
  
  

• Leoang

  I've got the same problem with the release of VS 2005. I'm currently attached to the previous version of VSourceSafe.
  
  

• Tanveer Rashid

  By the way, I meant to mention that as a workaround you should be able to perform an Undo on the pending adds for the items in the Bin directory rather than checking those adds in.  Once you undo the adds, VS should no longer try to control those files.
  
  --Ben
  
  

• hanshanshans

  Jason and/or Graham,
  
  OK, I need to figure out if the fix is absent on Beta 3 (despite our sourcebase showing that it's present) or if there is hole in the logic I used to fix this (seems more likely ).  To rule out the first I would appreciate it if one or both of you could try:
  1) Create a new C# ClassLibrary project and solution.
  2) Right click the solution in Solution Explorer and Add New Website (ASP.NET WebSite, C#, Local Filesystem).
  3) Right click the website in Solution Explorer and Add New Reference to add a reference to the ClassLibrary project.
  4) Right click the solution in Solution Explorer and Add Solution to Source Control
  5) Checkin all pending changes
  6) Rebuild All
  
  Do the ClassLibrary DLL and PDB files that are placed in the website's Bin directory end up with Pending Add operations (including 'yellow cross' glyphs in Solution Explorer) or do they show up as uncontrolled
  
  Thanks in advance,
  Ben Ryan
  
  

• dbrasco

  This is an issue my team and I are running into, as well.
  
  

  Ben Ryan wrote:

  The underlying issue is that Visual Studio is supposed to recognize that the binaries placed in the Bin directory are not intended to be source controlled.

  
  
  The context menu that displays for files in the bin directory shows all of the source control options, such as "Check Out For Edit Now", "Get Latest Version", etc.  This occurs with .dll, .pdb, and .xml files alike.
  
  

  Ben Ryan wrote:

  Were the put in the binaries directory as result of a project reference from the web project to a C# project and a build of the solution/C# project   Or were they put there by some other means

  
  
  In our scenario, these files were placed in the bin directory via project references.
  
  Thanks,
  Jason Bice
  

• felixflores86

  Ben,
  Ok, so the 'Save All Files' and Compare highlighted some changes I hadn't checked in which explains the .sln and vsssc. What I don't understand is why I would have more than 1 .vsmdi file. Perhaps this is part of the issue..
  
  The Bin issue persists though. Could this be something to do with my workspace
  
  Thanks,
  Graham
  

• Rudolf Betak

  I'm not sure why there is more than one .vsmdi file.  Do you have two different test projects in the solution
  
  It is doubtful the Bin issue is affected by your workspace.  The underlying issue is that Visual Studio is supposed to recognize that the binaries placed in the Bin directory are not intended to be source controlled.  Even if you manually add the binaries to SCC using Source Control Explorer or the command-line, Solution Explorer should not show SCC glyphs for the files nor SCC context menu verbs. 
  
  The files that are in the Bin directory ...
  1) Are they binaries (.DLL, .PDB)
  2) Were the put in the binaries directory as result of a project reference from the web project to a C# project and a build of the solution/C# project   Or were they put there by some other means
  
  Are you running Beta3 or Beta3 Refresh Team Foundation bits
  
  Thanks,
  Ben Ryan
  
  

• anfortas

  Ok, I'm back. I've since converted my team to TFS B3R and all the IDE's to RTM VS2005 Team editions.

  I'm still experiencing the issues I outlined previously. The only thing I can gather is that something about my old solution or project files (created in TFS Beta 2 with VS2005 TS RC1) have some conflicting code etc.

  Has anyone actually come up with a solution to STOP Visual Studio from checking out .dll/.xml/.whatever from the bin every time you build the project etc.

  Thanks,
  Graham

  
  

• Cherry 00613

  Ben,
  Ok, so this step by step approach worked. The Classlibrary1.dll and ClassLibrary1.pdb show up without the 'yellow cross' glyph (or any other icon) in the Bin directory. 
  
  The 'blue lock' means something is under source control right
  
  Perhaps the basis of this issue is the version in which you initially create the solution in Because my team started in Beta 2, before going to RC1 last month ( )..
  
  Thanks,
  Graham

  
  

• needforhint

  Hey Ben,
  Yes, my 'Bin' directory is part of Web Project with approx. 8 other C# projects that make up components in my app.
  
  I will try a Save All Files and run a compare between the .sln and .vssscc file to see if anything is different.
  
  I'll let you know what I find.
  
  Thanks,
  Graham
  

• N105le

  For what it's worth, our team is not on TFS (yet).  We're just running VS2005 and VSS2005.
  
  

• WilsonNg

  The blue lock does indeed indicate it is under Source Control.
  When you converted to RC1 and VSTF Beta 3 how did you place the old Beta 2 solution in the Beta 3 repository   Did you use Add Solution to Source Control or did you add the solution via the command line or Source Control Explorer
  If the solution was added to the repository without going through Add Solution to Source Control, that could explain why the files in the Bin directory end up controlled.
  
  Thanks,
  Ben
  
  P.S.  Thanks for you feedback on this issue.  I've had at least one other thread describing the same problem in Beta 3, so any help tracking down the problem is appreciated.
  
  

• .NetDeveloper

  Ben Ryan wrote:

  I'm not sure why there is more than one .vsmdi file.  Do you have two different test projects in the solution

  
  I actually have 4 different test projects in my solution. 3 that test layers and 1 for UI Load Testing.. : ) 
  
  

  Ben Ryan wrote:

  The files that are in the Bin directory ... 1) Are they binaries (.DLL, .PDB)

  
  Yes, all files in the bin directory are .DLL, .PDB, and .xml
  
  

  Ben Ryan wrote:

  2) Were the put in the binaries directory as result of a project reference from the web project to a C# project and a build of the solution/C# project   Or were they put there by some other means

  
  A few of the DLL's are references to C# projects within the solution. The rest are 3rd party controls. Namely, Infragistics 2005 Vol 3 (for .net 1.1), ChartFX For VS2005, and WilsonORMapper.
  
  

  Ben Ryan wrote:

  Are you running Beta3 or Beta3 Refresh Team Foundation bits

  
  I am running Beta3 as a single Win2k3 server on a VMWare Instance.
  
  Thanks,
  Graham
  
• Build always checks out most of 'Bin' directory? (VS2005 Team Suite RC1)