Extension stopped working until disabling and reenabling (persisting through restarts) about gitdiffmargin

[theglobe]

I am experiencing this in VS 2015. Disabling and re-enabling does not fix this, neither does Uninstalling and re-installing.

I had documents open when I tried the above, so it seems not to be related to #456.

How can I troubleshoot this?

[horeaper]

Found the same problem in 3.12.1 with VS 16.11, fixed with the same way.

[horeaper]

VS 16.11.5, the problem are still there, however disable/re-enable only works sometimes now. Also the command "GitDiffMargin.NextChange" and "GitDiffMargin.PreviousChange" is not working.
My git version is 2.32.0.windows.2

[PixBob]

I experience the same as well on VS2015, C++ /.Net Projekts
Someday the plugin stopped working, so far I do not get it running again.
Neither restarting VS, nor uninstall and reinstalling the plugin (restarting VS each time), brought the plugin back to show something.
Changes to the repository are not shown at all.

Is there anybody out there knowing how to fix it, I really love this plugin, it helps me a lot navigating through the the files...

[irontoby]

Same thing has just happened to me with VS 2022 Professional. It was working fine for me but then I had a separate issue which caused me to run a "repair" on the VS installation. Afterwards, this extension is no longer working in one of my repos. I've tried disabling/re-enabling, uninstalling/reinstalling etc.

At first I also ran into this issue. I re-cloned my entire git repo which fixed the problem of VS not recognizing the repo but this extension is still not working with that repo.

I tried creating a new solution for a console app in VS and then created an empty local git repo for it, also through VS. This extension didn't work for that solution at first, but after restarting it's working for that solution. It's still not working for the original solution.

So the problem has something to do with the git repo itself. The only other odd thing about this repo I can think of is that I have multiple worktrees configured.

I'm still doing more investigation, but if there's any place where I can see any logging / output for this extension that would probably help!

[irontoby]

Update: I re-cloned my repo using Visual Studio instead of the command-line, and the extension worked with that copy. I then updated my Git for Windows to the latest version, re-cloned with CLI and that one worked too.

So it appears to be an issue with a repo that was cloned using an older version of Git. Still not sure what the issue is, but for anyone who has this issue I'd recommend updating your CLI to the latest version and re-cloning your repo to a new location using either the latest CLI or the VS GUI.