36

Today, while trying to publish an app so I could test it, I suddenly got this error message:

The item D:\ScratchSrc\TryNewReportViewer2017\TryNewReportViewer2017\TryNewReportViewer2017.csproj.vspscc could not be found in your workspace, or you do not have permission to access it.

That's a mystery to me, as I've never gotten this before and I was working with this app just last week. Publishing it, too.

I've looked for the .vspscc file. 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?

I'm working with VS 2017, TFS 2015 on premise.

Rod
  • 4,107
  • 12
  • 57
  • 81

5 Answers5

14

This issue may due to the wrong source control binding for that specific xx.vspscc file.

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 .

PatrickLu-MSFT
  • 49,478
  • 5
  • 35
  • 62
  • 1
    But why would it suddenly be an issue? How would the source control binding change? – jbyrd Aug 23 '17 at 19:32
  • 2
    @jbyrd It's hard to determine the root cause. `.vspscc` is a Source Code Control (SCC) file for projects created with Microsoft Visual Studio; contains metadata used for tracking revisions of Visual Studio software development projects; includes information such as the version number, file path, and the number of nested projects. If this file got some issue, this may related to source control binding. Why source control binding change , may be related to local workspace issue, file changed , merge issue and so on. – PatrickLu-MSFT Aug 24 '17 at 10:00
  • The file is not in the source control, I've deleted the project folder and also the source bindings, did the clean get and the problem still persists. – Hrvoje Batrnek Nov 29 '19 at 13:11
4

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.

cskwg
  • 790
  • 6
  • 13
2

If the csproj.vspscc is missing you can create a new one by removing the project in visual studio and adding it back

paying back
  • 21
  • 1
1

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.bim. Was able to do both of these things without getting the error.

Bigfoot Hunter
  • 11
  • 1
0

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 2019 was a few months old so upgraded to the latest. That fixed it!

Jon Eldridge
  • 169
  • 2
  • 7