Vault Client 3.1.5 still checking in Bin (w/ VS 2005)

Speedbird · Post by **Speedbird** » Fri Nov 18, 2005 6:30 pm

Hi,

I thought this issue had been resolved.

However, I recently upgraded two web projects from VS.NET 2003 to VS 2005, on a machine with Vault Client 3.1.5.

Some files in the Bin folder of the web site project still get checked in. I believe the bug is in Vault, because when using the Team System source control provider, this does not happen.

I am not sure why some files get checked in and others are (correctly) ignored. It's not by file type: .dll, .xml, and .pdb all get checked in.

Thanks for any help,

SA.

dan · Post by **dan** » Mon Nov 21, 2005 2:16 pm

Microsoft was supposed to have fixed this, but perhaps they only did so for Team System. We'll need to check this out here and report back.

gmagana · Post by **gmagana** » Tue Nov 22, 2005 6:19 pm

Same behavior observed here... The file that is being checked in has the CopyLocal (or is it LocalCopy?) set to true... This is the only thing special about this dll in /bin.

dan · Post by **dan** » Wed Nov 23, 2005 4:13 pm

Ok, I've also seen it now, and yes, it is the same issue that MS was supposed to fix. Unfortunately, this is still not under Vault's control.

Actually, it looks like it was fixed for brand new projects created in VS2005, but converted projects exhibit the same behavior as before. Speedbird, is that the difference between Vault and Team System that you are seeing, or does Team System also work with converted projects too?

Also Gabriel, where are you seeing the CopyLocal property? It isn't showing up in the properties dialog in VS2005, so I'm not quite sure where that info is being set.

Note that MS identified a workaround previously: See http://lab.msdn.microsoft.com/ProductFe ... 4abc9c4005

I'd suggest contacting MS about it - there is more liklihood of seeing it addressed the more people report it.

dan · Post by **dan** » Wed Dec 07, 2005 11:25 am

MS removed my comment on the previous bug, but someone else added a brand new bug related to VS2005 checking in the bin folder. It is now :

http://lab.msdn.microsoft.com/productfe ... 91d7e1e2d1

So, pile in there - so far MS claims not to be able to reproduce it...

Alexandre · Post by **Alexandre** » Sat Dec 10, 2005 3:46 pm

Hi all,

I also have this problem with web projects. This is a major issue, it makes it very hard to have a team working on the same site project. How come there are so few complaints about this bug? Is there a workaround? I tried to flag the bin folder as not read-only and it still tries to checkin dll, xml and pdb files...

dan · Post by **dan** » Sat Dec 10, 2005 9:34 pm

It seems that Microsoft fixed this for some cases, but apparently did not get all of them.

Since MS is saying they cannot reproduce it, I would suggest adding a vote for the bug at the link above, or perhaps even adding an additional bug. The issue is definitely within VS 2005 somewhere.

Did you try cloaking the bin folder in the Vault GUI client, and then restarting Visual Studio? That was a workaround that seemed to have worked for others.

Alexandre · Post by **Alexandre** » Sun Dec 11, 2005 5:59 am

No, cloaking the bin folder didn't work either. The interesting thing is that some .pdb files are included in source control (appear in pending checkins), some are not. I couldn't find anything that would differentiate one pdb file from another, both are not read only, none of them are in the source control store. Is there some kind of configuration file that would keep track of which files are included?

dan · Post by **dan** » Sun Dec 11, 2005 8:28 am

I'm confused now - if none of them are in source control, how is Vault involved?

Perhaps you could list the steps you are doing, or list the structure of the project, both in and out of source control.

Perhaps you could simply delete the bin folder from source control (from within VS perhaps), and also delete the reference to the DLL but then recreate it.

Alexandre · Post by **Alexandre** » Sun Dec 11, 2005 9:05 am

Maybe I wasn't clear enough. Some details:

We have several very large (1.000 pages or more) ASP.NET web projects and they all reference several .NET libraries that are compiled in the same solution. Everything is source controlled, using Valut 3.5.1 (Vault was our last hope). All programmers use their own machine for development. The usual bin folder checkin problems appeared and we tried several approaches to solve it, none of them worked. The last attempt was:

1) Delete all bin folders content from source control, using Vault Client.
2) Cloak the bin folder.
3) Open the VS 2005 solution, and compile the entire solution.

When each library was compiled, the corresponding .dll and .pdb files appeared in the Bin folder of the ASP.NET web project, as it should be. But some of them appeard with the + sign in front of them, and the pending checkins windows started showing these files (hence the bin checkin problem).

What we found weird is that some .pdb files had the + sign, some had not. And there were nothing different among them, all are plain C# libraries. Any clues?

dan · Post by **dan** » Sun Dec 11, 2005 4:03 pm

I think you would need to cloak the folder from within Vault (meaning it wouldn't be deleted in Vault) for the workaround to have any effect.

I would contact MS at the forums above and ask them what the status is on the problem, which is definitely within Visual Studio. They may need a sample project to reproduce it on, and you may get more attention from them if you log a brand new bug rather than adding to the existing one.

gmagana · Post by **gmagana** » Mon Dec 12, 2005 12:48 pm

These threads have a couple of suggestions of things to try, but none of them worked for me

http://forums.microsoft.com/MSDN/ShowPo ... 4&SiteID=1

http://forums.microsoft.com/msdn/showpo ... 4&siteid=1

gmagana · Post by **gmagana** » Thu Jan 05, 2006 11:03 am

Just to update your guys, MS has posted some workarounds for this:

A hack-type one:
http://lab.msdn.microsoft.com/productfe ... DBK42838#1

One for VSS which may also work for Vault users:
http://lab.msdn.microsoft.com/productfe ... DBK16721#1

And the last one, this might be one for the books since MS says "... or switch to something like Subversion ...":
http://lab.msdn.microsoft.com/productfe ... DBK24492#1

EDIT: Oops, it seems anyone can add a workaround, so disregard what I said about MS adding that Subversion comment...

lbauer · Post by **lbauer** » Thu Jan 05, 2006 11:33 am

Thanks, we'll test them out.

ismangil · Post by **ismangil** » Thu Jan 12, 2006 6:16 am

Switch to the web application model http://webproject.scottgu.com/. Solves all bin dir source control problems.