4.1.4 is adding /Bin folder and DLL's

[neal007]

I'm using Vault 4.latest and I'm adding a ASP.NET 3.5 Web Site to Vault. Using the VSIP client (whatever it's named now) and when I add my solution to vault the /Bin folder is being added, DLL's are added, everything is added! Why aren't my exclusions being honored?

VS 2008, Windows Vista x64 SP2...

[Beth]

The exclusions listed in the Vault admin web page will not affect Visual Studio due to the way Visual Studio adds solutions to source control. Those exclusions are if a folder is selected and added, then some items under that folder can be automatically excluded. Some users want just a few items such as 3rd party DLLs, so they can directly select those DLLs and click Add to force an add. VS adds each item individually, which then overrides the exclusion list.

Are you using the Classic Client or the Enhanced Client?

In some cases, you will have the option to "Exclude from Source Control" which would show up in the right-click menu (see attached image). You can also uncheck items in the Pending Checkins so that they don't go into Vault or delete them from the Pending Checkins depending on which client you have set.

[neal007]

VSIP client (enhanced vault integration) and as it's a web site (not web app) and an existing site in the file system, I don't have that option. I did look for it!!

[Beth]

The best thing you can do from here is to manually remove the items from the pending check-ins or just not check them to be checked in. If they are deleted from the pending check-ins pane, then they shouldn't give you more grief.

I also have a feature request open to add the Exclude from Source Control to the Enhanced Client (VSIP) that I can add your vote to if you would like.

[dplante]

I'm using Vault 5.0.1 enhanced client. Has the "exclude" feature been added to this version?

[dplante]

I have just started using 5.0.1, and do as you suggest: manually uncheck folders to be excluded. But, I am wondering if the feature you mention was added to this version, or if there are any plans to do so in the future.

[Beth]

We still have the feature request open so it's still a candidate for a future version. I can add your "vote" to that feature request.

[MikiWatts]

Please add my vote as well. I'm having the same issue.

[Beth]

I have added your vote. Thank you for the feedback.

F: 12874

[aaron_smith]

We have been vault users for a few years now. Recently we became Microsoft Certified Partners and were given Team Foundation Server for free with our subscription to MSDN. I installed beta 2 of TFS 2010 just to try it out to see what it's all about. One of our biggest pain points (yes, it is a pain point) is this exclude from source control. We use the enhanced client and we have certain files (such as licenses.licx) that frequently get touched by visual studio. Having 3 developers have conflicts with this file is insanely painful. So we did the work around of removing it from vault and then undoing the check in, etc. Then this broke our build process and we had to do a work around to copy that file back in on our build server... Add this to many projects and we are tired of not having this stupid little feature. TFS has it in their client, at least in the latest version. So unless this feature gets added very very soon, we are going to switch. Are there plans to put this in the next version?

[Beth]

If you exclude from source control on that file, it still wouldn't get to your server automatically from Vault. Maybe I'm missing something, so could you explain further how the exclude from source control would fix the build?

I'm thinking some other option like working in .cvs mode and making the licenses file a mergeable file might help you better here.

[aaron_smith]

It's not that it's breaking because it's not there. It's breaking because it DOES make it in there when one developer happens to check it in by accident. Then when that developer happens to accidentally check it in, now the other 2 developers are stuck not being able to do any work until that one single file gets fixed with the work around....

The biggest question is, why hasn't this been just added as a feature? This is something that was there in the classic client and people have been asking for it for years. Other source control vendors do it, and they do it because it's a useful feature to have. It stops a lot of little stupid pain points. We have to deal with it on other files that we cannot have checked into source control that have to be parts of projects but kept out of source control for one reason or another and it's starting to become more of an annoyance now than ever. I even asked the other developers if I am just making an issue out of nothing and they all agreed that it is needed and they use it all the time in other products.

Don't get me wrong, we've been extremely happy with vault and we have very few complaints at all. But this is one thing that is just silly. It really needs to be there to solve little annoyances.

[Beth]

It's breaking because it DOES make it in there when one developer happens to check it in by accident.

Thanks for the clarification.

We definitely think it's a good idea and have talked about getting it into a release. I'll see if I can find out more on this.