Exclude web project Bin folder with VS.2005

[kcunningham]

When running a web project in directory base mode with VS.NET 2K5 the web project is pretty much no existent but we have an issue with Vault sucking in project related assemblies. The issue is that during a build it will (obviously) need to overwrite the assembly in the bin file to update the version except for the fact that this file now becomes a contention point. Of course, we do not want to version our references at this level - our build can handle all of this.

My question is: Can I tell Vault (or solution file which vault can read) to not include a particular sub directory? I am having developers "Check-in Recursively" and getting the \bin folder included.

[dan]

I'm not quite following the scenario. Is this checking in from within Visual Studio, or the Vault standalone client?

I believe there is an Exclude From Source Control option you can apply from within Visual Studio if you want particular files excluded.

[kcunningham]

Thanks Dan.

I may have done a poor job explaining the situation so I am going to try again. With VS.NET 2K5 there are no more web project files when using file based web sites, everything is pushed into the solution file. Therefore to VS.NET 2K5, everything underneath the web diretory is "fair game" and is published to the web. Matter of fact, the "Exclude from Project" context menu does not even exist.
So, for example:
1. Let's say I have WebProject1 as my main web site. At this point I only have one project in my solution file - WebProject1.
2. I now want to add some business logic so I add ClassProject1 to the solution.
3. Next, I a reference to ClassProject1 from WebProject1.
4. Add solution to Vault. (NOTE: Before building, let's assume we know it's ok )
5. Now Build. You will notice the references are underneath the web site in a \bin folder. Vault now assumes this file is part of the solution - it will have the "New File Added" icon next to the file.

Step 5 is what I would like to tell either Vault or the .sln file to exclude.

I have included a test project using the names above for better explanation.

Kevin Cunningham

[dan]

I would guess that it is Visual Studio doing this and not Vault, because when a project is under source control, it is VS that decides which files are added rather than the source control provider. One way to verify is to make VSS the default provider and see if it handles it differently.

I will look into this in the next few days, but you might also post to the VS 2005 forums and ask about it there as well.

Thanks,

[kcunningham]

Thanks Dan. I'll check back in a few days. In the mean time I'll make a post on the MS forums.

[dan]

I was able to reproduce this, but it does look like VS is sending us the files to add to source control, and we have to do what it is telling us.

Also, you are right, the Exclude from Source Control option appears to no longer be supported.

Have you had any luck getting answers in the VS forum?

[Guest]

It IS visual studio doing so, and it is a filed bug with MS.

For me it is major - it totally ridicules development of more complex web environments/scenarios.

But there is nothing that sourcegear should do about it. This is only MS' fault.

[kcunningham]

Thanks for looking into it. I do not have any responses yet but I will post back here if I get one. It's a pain but we can manage. I was also able to recreate it in Visual Source Safe so you're right it's affecting users of both Vault and VSS. I image this is going to bite alot of people

Here is the post in the MS forums. 14 views in 2 days ... grrrr

http://forums.microsoft.com/msdn/ShowPo ... ostID=6338

[kcunningham]

This issue has already been entered into the VS.NET feedback site and has been validated as a legitimate issue. The work around is to mark the "\bin" folders writable and then "Cloak" the folders. This actually works really well.

http://lab.msdn.microsoft.com/ProductFe ... 4abc9c4005