Visual Git 208 add-in fails to run under Windows 7/Visual Studio 2010

Sadly that’s almost all the information I have at the moment.

The installer for Git Extensions 208 runs fine, the setup for Git Extensions validates fine, with green for all settings, Visual Git opens fine with Visual Studio 2008.

  • Code publish through jenkins for .net MVC solution in Ubuntu machine
  • Reverting to a previous commit in Git for visual studio 2012
  • What is the right way to add .NET project with NuGet dependencies to a git repo?
  • Include Git revision number inside .NET project
  • web.config and app.config machine-specific settings in git
  • SvnClient.GetStatus(path, args, statuses) returning 0 for versioned file?
  • But, going into Visual Studio 2010 gives me a dialog:

    The Add-in 'Visual Git' failed to load or caused an exception.
    Would you like to remove this Add-in?
    If you choose yes, the file it was loaded from,
    '\\myFileServer\home\myUserName\Visual Studio 2010\Addins\GitPlugin.AddIn',
    will be renamed.
    Error Message: <Unknown Error>
    Error number: 80131515
    [Yes] [No]

    Visual Git then fails to load.

    Is the issue that the Visual Git files are being hosted from a file server? That’s all I can think it might be…

    Has anyone seen/solved this before?

    EDIT: Before anyone asks, the title does not contain a typo of “2008”. Git Extensions claims to work with VS2005/2008/2010. The fact that it’s also at version 208 is a coincidence, as far as I know.

  • Very long-historied file in Git repo suddenly has blank log and is invisible to “git status”
  • How to avoid typing passphrase for git pull executed under www-data
  • Correct use of GNU Global tag files in different Git branches
  • Grunt-shell save command output as variable
  • Break linear git commits into two merged branches
  • Merging two folders using git
  • 5 Solutions collect form web for “Visual Git 208 add-in fails to run under Windows 7/Visual Studio 2010”

    There is a known issue causing this. The work around can be found in the Git Extensions issue tracker:

    I ran into this problem, but found a solution.

    I am running Visual Studio in a virtual machine on my MacBookPro. I’m using Parallels to run the virtual machine. Because of the way Parallels works my documents folder is actually technically a network share pointing back to MacOSX. And apparently Visual Studio 2010 doesn’t like network shares for addins by default.

    It looks like that is the problem the OP encountered as well looking at his error message.

    To get it working, you have to add the loadFromRemoteSources element (see the MSDN reference) to the “C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe.config”:

          <loadFromRemoteSources enabled="true"/>

    I did that and it immediately loaded up and started working.

    BTW, full attribution: I found the solution here.

    This didn’t work for me until I looked at the comments here:

    Under Vista or Windows7 take care of thefile system Virtualization.
    Editing devenv.exe.config might result in creating a copy under

    \Users{%UserName%}\AppData\local\VirtualStore\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe.config

    leaving the original file untouched. This depends on your user settings.
    It might help to open “VS 2010 as administrator” (or another XML-Editor of your choice),
    edit devenv.exe.config, inserting the

    tag, save the file and close.
    This will edit the original file, not the virtualized copy.
    Having done so referencing “remote” assemblies in your projects
    should work

    For anyone who can’t get to Henk’s link above: The issue (for future Googlers) is that the Git extension doesn’t work if it’s run from a UNC path (\\server\some\path) and has to be installed in a local directory. You can add a local directory via the Tools > Options > Environment > Add-In > Macro Security menu.

    My solution was to replace the Addins folder (which was network remote) with a symbolic link to a local folder using mklink. This effectively does the same thing David Moles has suggested.

    Git Baby is a git and github fan, let's start git clone.