Comments
Sort by recent activity
I am still having the issue after upgrading to 3.3.19183. The xxx.sqlproj.vspscc and xxx.sqlproj files get checked out but no changes are made to them. / comments
I am still having the issue after upgrading to 3.3.19183. The xxx.sqlproj.vspscc and xxx.sqlproj files get checked out but no changes are made to them.
Eddie, I don't see any errors in the log. Attached is the log. The xxx.sqlproj.vspscc file exists in the same directory as the xxx.sqlproj file on my local machine but it was not in TFVC (Team Foundation Version Control). I tried adding the xxx.sqlproj.vspscc file to TFVC and the error goes away. However, when I open the solution the xxx.sqlproj.vspscc and xxx.sqlproj files get checked out but no changes are made to them. This causes an unnecessary checkout and therefore lock on the xxx.sqlproj file preventing other developers from working on the project. / comments
Eddie,I don't see any errors in the log. Attached is the log.The xxx.sqlproj.vspscc file exists in the same directory as the xxx.sqlproj file on my local machine but it was not in TFVC (Team Founda...