Vspscc file missing

You wont need to restart VS. Here is my list I did a quick test and I think you can copy this directly. Skip to content. Star New issue. Jump to bottom. Labels bug. Copy link. Hi There, Thanks for the response. I'm guessing there is Thanks, Chris. IsNullOrEmpty Options.

AddRange Options. Convert p. Sign up for free to join this conversation on GitHub. Publishing it, too. I've looked for the. Found it exactly where it said it should be.

So, the alternative is that I don't have permissions to it. I don't understand why I shouldn't have permissions to a file on my machine that I created, but whatever. So, how do I get permissions to my own file? This issue may due to the wrong source control binding for that specific xx. Double check your source control bindings for that file in TFS. You could also try to unbind and rebind the file. Then delete the file in local back up local changes first and get latest version from TFS.

Finally do the publish again. If above solution is still not working, try to delete local workspace and create a new one, get latest version of the file, modify the file with local changes if you have in your backup , check in the file, then do the publish. Another reason for this problem is, that the vspscc file is not checked in.

Just do a "Compare" on the project folder to see, if it's missing. If the csproj. I was able to 'fix' the problem by going to the source control explorer, selecting the smproj file which was checked out for editing , and checked it in by itself. Then, I checked in the Model. Was able to do both of these things without getting the error. I also tried all the usual things, deleting the entire solution directory, getting it from TFS again but nothing worked.

Noticed the version of Visual Studio was a few months old so upgraded to the latest. The text was updated successfully, but these errors were encountered:.

Also when we update NuGet packages, if the vspscc file hasn't been added to TFS every project being updated results in a warning dialog popping complaining it can't check the vspscc fiel out. So we have to go through projects and manually add the vspscc file. Sorry, something went wrong. Visual Studio is no longer adding these files to TFS. However, if there is any system that is still requiring these file exist, and for no other reason than to exist, that needs to be fixed.

I've looked at all the threads since and not one person from Microsoft could explain their use. The only thing that I did find is that they had an intended purpose of containing files to exclude from source control, but that purpose never manifested. VS Do you think if I delete them they won't come back? Or, client side workspaces? When using server side, it no longer adds the files to Pending Changes.

Client side adds all files of virtually all types, with few exclusions. Client side requires manual management, so I don't really know what to tell you. If there is currently an issue with NuGet, then I would say yes, until the issue is addressed. I've been waiting for this annoyance to go away for about 10 years now. Visual Studio does not add them. It seems to be a Visual Studio UI issue then.

The error in this case is: The item [path][project]. I get that error from time to time, usually when I "go online" after I've been disconnected from TFS, but sometimes during a NuGet operation too. This is so painful. Not only do I have dialogs to OK everytime, but it takes so long inbetween each dialog appearing. A waste of time! So what is the workaround? Do I delete them? Do I check them into TFS until such time as the issue is resolved?

Yes add them to TFS. It's the only way. PhilPJL Thanks, that helps! I added the following to our. That's not going to stop VS from checking them out and cluttering up pending changes whenever you update a nuget package. BTW, this seems to have gotten worse with VS I can say my frustration level has significantly increased from VS -- almost entirely because of pop-ups in various areas.