Visual Studio 2008: File history/blame shows the current line

[lukastvrdy]

Hello,

I'd like to request feature in VS plug-in for showing git blame.

Currently when I want to see the blame, I do this:

1. Right-click on line in the source code (e.g. line 385)
2. Select "GitExt: File history"
3. Click on the blame tab
4. Scroll to the line 385

Expected behaviour:

1. Right-click on line in the source code (e.g. line 385)
2. Select "GitExt: Blame"
3. File history/Blame tab is shown and showing line 385

[vbjay]

That menu option is referring to the file not the line. However, that is
not s bad idea to go to the line.

On 3:07AM, Tue, Jun 23, 2015 Lukáš Tvrdý notifications@github.com wrote:

Hello,

I'd like to request feature in VS plug-in for showing git blame.

Currently when I want to see the blame, I do this:

1. Right-click on line in the source code (e.g. line 385)
2. Select "GitExt: File history"
3. Click on the blame tab
4. Scroll to the line 385

Expected behaviour:

1. Right-click on line in the source code (e.g. line 385)
2. Select "GitExt: Blame"
3. File history/Blame tab is shown and showing line 385

—
Reply to this email directly or view it on GitHub
#2839.

[ajilani]

I still don't see the new option in VS. Tried modifying the installation to include all VS integration, but still don't GitExt:Blame in the right-click menu for a line of code, just the three old options.

• GitExtensions 2.50
• Windows 10 Pro 1703 build 15063.413
• VS Professional 2013 12.0.40629.00 Update 5 (with ReSharper)

[lukastvrdy]

I tried it in MSVC 2013, but I don't see it there. Could you, please provide steps how to get into GitExt: Blame as was requested in this ticket?

[jbialobr]

It is in the GitExt menu, but it is not in the context menu - as requested.

[crypto-rsa]

I am using VS 2015 and I was able to add it through
Tools - Customize - Commands - Context menu: Editor Context Menus | Code Window - Add Command

Does it not work in VS 2013?

[ajilani]

I could not get either of these to work in VS 2013:

[jbialobr]

It looks like you have an old version of the extension installed.

[lukastvrdy]

Works for me in MSVC2015. FYI I don't see it in MSVC2013 though.

Thank you for implementing this feature ;-)

[RussKie]

I suppose we can close it.
The feature is available, albeit it may not work in older versions of VS.
We won't be back-patching any old versions.