In my case, the commands were number 9-11, you might have to do some trial-and-error here. Problem is that the custom commands are not shown with their title but only as External Command X with X being the number of the external command. Now to add those new commands to the file tab context menu, go to TOOLS-> Customize., select the Commands tab, click the radio button Context menu and then select Other Context Menus | Easy MDI Document Window. If you omit the /startrev and /endrev parameters for the blame command then a dialog is first shown where you can specify more options for the blame. Notice the /line: parameter: this will make TortoiseBlame automatically scroll to the same line the cursor is located in the opened file in Visual Studio. /command:blame /path:"$(ItemPath)" /line:$(CurLine) /startrev:1 /endrev:HEAD.Since I add my commands to the context menu of the open file tab, here's the parameters I used: The first step is to add the TortoiseSVN commands as external tools, under the menu TOOLS-> External Tools.Īdd the name of the command, the path to TortoiseProc.exe and then the parameters for the command. Those plugins also have the advantage that when you do refactoring, they automatically record the renames and moves in SVN. Of course, there are Subversion plugins for Visual Studio like AnkhSVN or VisualSVN, with the latter already using TortoiseSVN for many of its UI. If you're using Visual Studio, you can integrate TortoiseSVN commands to various context menus.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |