Short Question
Has anyone had an issue when right clicking files (.c/.h/etc..) and the TortoiseSVN menu is not present? Note that it is there when I right click a folder in the same directory.
Failed Attempts
I have seen that a number of issues like this have been resolved by running the installer again and selecting repair or modify, at this point neither of these attempts have worked.
Is there anything else I can try to get this working again? The DIFF functionality being gone is hurting something fierce.
Edit
I am the only developer working on the files. I actually found a way to see the diff: Move the parent folder TortoiseSVN->Check for modifications. This menu does indeed show all of my versioned files as well as any of them that have been modified.
I have also confirmed that the files really still are version controlled by checking out the same repo in on a different machine.
Edit2
It is worth noting that I am using Macdrive and it's right click menu is present all the time. In addition, I just saw that I am having the same issue with TortoiseGIT as well.
Go to registry editor using regedit
Go to and click on HKEY_CLASSES_ROOT/*/​shellex/ContextMenuH​andlers/TortoiseSVN
Observe error message box saying access is denied.
Right click on the key mentioned above, go to "Permissions"...
In the permission dialog, click on "Advanced"
Click on "Owner" tab, click on your account and click "Apply"
OK the dialog
Right click on the key mentioned above, go to "Permissions"...
Grant permissions for OWNER RIGHTS to "Full Control"
Apply the changes
Source
If still not works so try to use shift key + right click.
Are you sure that these files under version control? It is possible that someone has deleted these files from svn repo and after update your these files has become unversioned.
You can check that by going one dir level up (from folder where these files are located) and choose whether Tortoise-SVN->Repo-Browser menu (check that they are present on SVN server) or SVN Commit (make sure Show unversioned files checkbox is set and check Text Status Column if it contains "non-versioned") .
Shift + Right click on the folder which you want to checkout click TortoiseSVN --> settings --> Context Menu --> uncheck the Hide menus for unversioned paths
Related
I have SnailSVN client on my Mac machine, however I can't seem to find an option for deleting remote SVN branch. Is this option possible through this SVN client?
the context menu options are available only in the right window of Repobrowser. You must see main SVN directory on the left side and all the folders on the right. Do not try to find 'delete' option selecting your project folder in the left window, just try to find it when you literally see your folder in the right.
Compare these two screenshots: left window context menu VS right window context menu.
I accidentally hit "Get Latest Version" on item in TFS with which I'm not currently working on. This made name of the item visible in black in Source Control Explorer, which is misleading to me since I'm used to identify objects which I'm working on visually. How can I reverse this operation?
To make the item in Source Control Explorer gray out again. You could try below workaround, get specific changeset 1.
Open team explorer
Click Source Control
Right click on you file/folder
Select Advanced Click on Get specific Version
Choose Changeset Type and enter 1
The item in Source Control Explorer will gray out again. This is due to:
Changeset 1 is a special changeset on your Team Foundation Server
instance. It was created as part of the setup routine and only
contains one thing - the root node ($/) in your source control tree.
If you do a get for Changeset 1 on any actual files then they will not
exist at that point in time on the system so will be deleted locally
and the server will know this.
Note: This will change the status of your files to "Not downloaded" and will remove the local copy of the file. It will only remove files that were put there by TFS.
Assuming you are using TFVC, you can also try cloaking the folders that you don't need. This will "remove" the any unchanged files locally and exclude the folders when you get latest in future.
In the Source Control Explorer, right click on the folders that you want to exclude and go to "advanced" then select "cloak".
To start using the files locally, you can go to the same place and select "uncloak".
I am working on a solution (a very big solution), and I want to check if I have left anything checked out. How do I see all the items I have checked-out?
And could you also tell me how to see all checked-out items by another user please.
simply pull up the pending changes window (View > Other Windows > Pending Changes) to see what files you have checked out!
http://msdn.microsoft.com/en-us/library/ms181395(v=vs.100).aspx
As for the other users, you would need to view the source control window to see who has checked out that file.
Simply go to View > Team Explorer then browse to the collection/project you are working on and double click on "Source Control" to open the source control explorer.
This then will show you the directory listing system where you can see who has checked out which file and what kind of check out.
also take a look at this: Can I check what files another person has checked out in Visual Studio 2010
I moved some code from my c drive to my d drive. When I opened the solution, it told me that:
The solution appears to be under source control, but its binding
information cannot be found. Because it is not possible to recover
this missing information automatically, the projects whose bindings
are missing will be treated as not under source control.
So I tried permanently removing the bindings and downloaded the latest version. Now my changes don't register as pending changes.
I've tried selecting the solution in the Solution Explorer and File => Source Control => Change Source control, but it does not let me bind. Server Name and Server Binding columns have "".
Generally speaking, the location of code on your machine is dependent upon where your workspace is located.
If you move your workspace to the D: drive, then there shouldn't be an issue.
However, if you simply used Explorer to copy the files to the new location, then VS isn't going to be able to maintain the bindings.
From the Workspace Editor you can map the entire tree, solutions or even individual projects to a new location.
First off, put it back and undo the changes.
Then, Go to File | Source Control | Workspaces.
Click on the work space name and then the "Edit..." button.
In the working folders area select the source control folder you want to move and give it a new local folder location.
You will need to edit your Workspaces for TFS Server to know the change that has happened at your local machine. To edit your workspace, in Visual Studio:
ensure you have no pending changes; also copy your source code folder to some location temporarily, just to be safe (you can remove after you are all set)
go to Source Control Explorer
locate the "Workspace:" dropdown
select the item "Workspaces" from the dropdown list (you will get a dialog titled "Manage Workspaces"
if you have multiple Workspaces, select the appropriate one from the list in the dialog
click on "Edit" button (you will get an "Edit Workspace..." dialog)
down below in the dialog, you will see "Working folders" grid
click on appropriate row from the grid and modify the "Local folder" path to set to your new folder location
Sometimes TFS and Visual Studio have issues in getting these workspace changes synchronized. I would always close Visual Studio and re-launch it to get my changes synchronized anytime after I make Workspace related changes.
Hope this helps.
the most crude way here (I don't know if there is any other way)
is to put the folder back to its old location , Check in your changes
then remap the project to the new folder
When you move files/folders to make the moves pending changes you need to use a TFS client to do the moves.
For one or two files the Team Explorer UI is OK, for more the command line is easiest.
See tf.exe rename on MSDN (tf move is an alias for rename). There is also step by step help on using the GUI: Move, Rename, and Delete Version-Controlled Files and Folders.
I've (apparently) checked-in (added) a file that shouldn't have been added to a branch. I need to revert this, but since then, 20 or so changesets have been added to the repository.
I'm used to working with Subversion, where it's only a few clicks and it's out. How easy is it in TFS?
TFS is a pain to use in general (personal and biased opinion). Here's a how-to article from Microsoft on how to proceed to revert changes back (warning: more than a few clicks away).
As given in that article, the steps to revert to a prior version of (a) file(s) are:
In Source Control Explorer, right-click the file whose changeset you want to roll back, and then click Get specific version on the
context menu.
In the Get dialog box, select the prior version of the file, and then click Get. For more information, see How to: Retrieve
Old Versions of Files from
Changesets.
After this file is in your workspace, right-click the file, and then click Check Out for Edit on the context menu.
Right-click the file again, and then click Check In Pending Changes.
In the Check In - Source Files dialog box, select the file, and then click Check in.
The Resolve Conflicts dialog box appears.
Click Resolve to open the Resolve version conflict dialog box.
Select Discard server changes.
Click OK.
NOTE: To review your decision before discarding the server changes, you can click Compare to view the server and local copies
simultaneously.
In the Resolve Conflicts dialog box, click Close.
In Source Control Explorer, right-click the file, and then click Check In Pending Changes.
In the Check In - Source Files dialog box, click Check in.
As #Darin has posted, you can simply Get the state of the previous version/changeset onto your PC and then check it in as a new version, thus undoing the effect of the check in. This is dead easy and can be done from the GUI, but does involve a fair bit of faffing around.
If you're happy to use the command line, you can also command TFS to rollback the changeset for you. This does all the "work" of the above option, leaving you with a changeset in your pending changes that will undo the checkin's effect, but hopefully with a bit less effort.
If it is added by mistake, you don't want to roll back. Instead, you want to tf destroy (from the command line) that file in each of the branches.
TFS can be a bear to work with if you add a file, delete it, then re-add a new file with the same name. It makes merging much more difficult.