4.0.2 VSIP client and Web Service project

[neal007]

I switched to the VSIP client and it wants to add every file in my /bin folder and of course fails to check-in because of this. Why is it wanting to add all of my web service project /bin files? DLL's, PDB's, etc.????

[jclausius]

I don't really know. I've met with our VSIP team, and discussed the issue. They're going to investigate, and check if Visual Studio is sending a different list to add a project in MSSCCI vs. VSIP.

The main objective is the VSIP client should try to have the same behavior of the MSSCCI client, but with more options at your fingertips. I'll report back when I have any info.

[ian_sg]

(EDIT: Never mind, that thread is mostly about the MSSCCI/ 2003-compatible client. I'll respond here.)

The only way I was able to get the contents of a bin folder included was to manually include the bin folder in my project. By default it is excluded. This seems like appropriate behavior to me. If you have not explicitly included a bin/obj directory in your project and are still seeing this, let me know.

I'll give you an idea what's going on here, so hopefully our design decisions seem less arbitrary and frustrating. Each Visual Studio project type implements a number of interfaces if it's going to support source control. One of these interfaces includes a function that is essentially "give me the files I should add to source control". It's possible for us to override or ignore this behavior, to look through the project ourselves and decide what should and should not be added, but obviously this should be done with caution. We assume the authors of the project types have good reason for what they're doing, and we only want to subvert their intent in the case of a clear-cut bug. So far, that doesn't look to be the case here.

I'll touch on the repository exclusion list briefly, which you mentioned in the other thread and is peripherally related here. We don't always exclude items in that list. On purpose. People often want to add .dll files, for example, to their source control repository. (I've done this in the past for third-party libraries for which I only have a binary, as one example.) Its current behavior is by design: the exclusion list is used only when a folder is added, which typically happens via the Windows GUI or command-line clients. When an explicit file add is requested we ignore that list, as we assume you explicitly added the file because you actually want to add it. The IDE clients (MSSCCI and VSIP) almost always do explicit file adds, because Visual Studio has given us a list of files, so the exclusion list is not consulted. Again, this seems like the appropriate behavior, as the Visual Studio project expects to be the authority on what files belong in source control. We'd only want to work around that behavior for an obvious bug.

So to restate more briefly: is the bin folder in question explicitly included in your project? If so, that's expected behavior. If not, let me know, and if possible let me know what steps you're performing to get to that state.