I have a website with several thousand pages that I have added to TFS source control. I have created a workspace with the local path mapping to the actual file directory (so that anytime a file is saved, the actual source file is saved as well). I have added my files and then checked them in.
After checking them in for the first time I see the lock symbol next to all of the files. Now if I go to check out and edit, I can check in my changes and this shows up in the changeset, but the file remains checked out. I can view the history and see all iterations (every time it was checked in), but it still always shows the file as checked out.
I think the issue may have something to do with the fact that I created the workspace as a particular user and then made it a Public Workspace. I now am logged in as a different user attempting to check in/out.
I also just noticed that in my history it shows the changes made by UserB, but in Source Control Explorer it shows checked out by UserA
When creating this project I set my workspace to the initial source code directory. I then set another user's workspace to this same directory (it was a shared drive). Visual Studio did not stop me from doing this because this local path was set on different computers, but I believe that this was the issue.
Related
The above error recently started being thrown when I was making updates to an existing C# windows app that saves a folder location for files it uses.
Upon receiving this error, I found that my whole hard drive seems to be set to read only. (recently had to build a new dev system) I have tried changing the folders back to being readable via folder properties. Dialog pops up and goes through all the files as if it were changing the properties. When I open the properties immediately after, the folder is back to read only.
I have also noticed that VS IDE does't save changes to the recent files/projects.
Anyone experience this and have the solution?
Things I have tried:
created a new admin user. Logged in and found the same situation. Not tied to my profile.
Tried command prompt changing folder attributes with attrib command.
Tried changing my users permissions to full control.
uninstalled OneDrive (to eliminate possible syncing issues)
Turns out my AppData folder hidden property was set to true. Setting this folder and all sub folders to not be hidden fixes everything.
I've deleted a file by accident. Then I created another file with the same name. When I tried to check in the change, it didn't work out and got an error. I undid the changes then deleted the file, there's no more error when I try to check in.
I'd like now to get the latest version of the file before I deleted it.
Thanks for helping.
In TFS, a deletion only takes effect when you check in the said deletion change, and thankfully, this operation is reversible.
Here are the most common recovery scenarios, assuming that the file already had revisions stored in TFS before the accidental deletion:
If the file is still visible in the Source Control Explorer and is marked for deletion (under the Pending Change column):
Then it means that you've deleted the file from your solution (and file system), but that you didn't checked in the changes yet.
Use the "Undo" command of its contextual menu to restore the file in your workspace to its latest version before deletion.
From there, you'll be able to add the restored file to your solution.
If the file is still visible in the Source Control Explorer and is not marked for deletion:
Then it means that you've deleted the file from your file system.
Use the "Get Specific Version" command of the file's contextual menu to restore it in your workspace. In the "Get" window, select "Latest Version" and enable both options.
From there, you'll be able to add the restored file to your solution.
If the file is not visible in the Source Control Explorer:
Then it means that you've checked in the deletion change.
Turn on the "View deleted files" option of the Source Control Explorer (usually the 2nd button of its toolbar) to see your deleted file.
Use the "Undelete" command of the file's contextual menu to restore it in your workspace.
From there, you'll be able to add the restored file to your solution and you'll eventually have to check in the undeleted file to make it available to others, since this file only exists in your workspace.
I've recently upgraded to VS 2013, and I'm seeing that my site's solution is automatically being checked out on opening.
I suspect that this is because the site uses Umbraco, and consequently the App_Data folder is often cleared down... Umbraco will then re-populate indexes and config files within that folder when the site is run.
I've believe I've excluded the App_Data source from source control (right-clicking shows an option to Add files to source control), and that therefore new items within that folder shouldn't affect the solution, but is that right?
I know if I create a new file in, say, the images folder in the solution that it will be automatically added to the project (which is quite handy)... is there any chance it's doing the same thing with App_Data? Is there a setting somewhere to alter that behaviour?
I have a Clear Case VOB mapped on my Z: drive in Windows 7 and checked out 2 files. All the other files are shown as read only in Visual Studio 2013 but these checked out files seem to be editable (no lock symbol like on the others), but when I try to save the file it only allows shows a "Save As" dialog and when I try to overwrite the file I get a message "Access to 'Z:...\khmwdkwdmx.d0c' is denied" (which I suppose must be some kind of generated temp file, because every time I try to save it always has a different name). If I edit the file in Notepad++ it can be saved as normal, no errors in that case.
Additional info: The problem seems to be that as I can't create new files in a clear case dynamic view only change the files I have checked out, so VS cannot create it's temp files while saving (like m4s1c0nk.swt, jl0lb2ob.255 and other random generated ones) so the file saving always fails. Is there any possible way to turn these file generations off or to generate them somewhere else?
First, make sure of the state of the files within the parent folder of Z:\...\khmwdkwdmx, to check if those two files are indeed checked out.
Second, verify is there is no other processes keeping an handle of those files, preventing Visual Studio to update the actual files.
You can also fall back to a Visual Studio session opening your view using the full path of the dynamic view (M:\MyView\MyVob\...) instead of the subst Z:\MyVob
The problem seems to be that as I can't create new files in a clear case dynamic view only change the files I have checked out,
Check if you can at least check out the parent folder, or check is associated right:
cleartool descr -l parentfolder##
(the ## are for describing the element, not the version, of the parent folder).
Try a:
cleartool protect -chmod 777 parentfolder
More generally, write issues are described in "About the error Checked out version, but could not copy data to <some-file.txt> in view", and are following "About ClearCase permissions on Windows".
I have some project saved in starteam. As there are a lot of obsolete files I can't check in or check out all project, only changed files. Now I copy project from one computer to another for other developer. I expect starteam treats copied project as new item for check in and check out, but it don't.
Forexample:
I modified file on first computer.
I update list of files on second computer and see this file in "check in" list, as I modified it on second computer.
It is incorrect.
I think there is some configuration file or something like, that saves computer (or user) settings. So when project is copied, settings is copied too.
Do anybody know how to change this configuration to set copied project as new instance of starteam???
You should be able to Right-Click on either the file or a close group of files (such as the Modified group) on the file tab within a project and choose the Update Status option. This will cause StarTeam to analyze the file to try to determine if they truly are the same as what is in source control. Then you can refresh the list and it should change most of your files to current.
There is also a configuration setting under Tools->Personal Options->File tab that is "Use file checksums (MD5) to calculate status". This may be useful to you as a different way to have StarTeam determine if the file on your local disk is the same as what is in source control.
It sounds like you are using a custom filter/query for your check-in list. The status for the files that are copied/moved would be "unknown" and they can still be checked-in by checking the "force check-in" checkbox in the check-in dialog. Just verify that the local version is correct by using compare contents before committing it.
You can try switching from a central file status repository to a "per folder" repository. This will create .sbas folders wherever you check-out files and should maintain status for local files when their containing folder is copied or moved. Look under Tools, Personal Options on the File tab under Repository.