Error loading DLL git2-3f4182d on Windows (module not found)

Open
#2,142 5 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
csharp, git
Domain
devtools, operating-systems

Research direction

Start by reproducing the Repository call in the Visual Studio 2022 extension on .NET 4.7.2, then inspect LibGit2Sharp.dll.config and the installed LibGit2Sharp.NativeBinaries deployment. Check how the Windows native DLL is located and whether the deployed architecture matches the extension; done means the repository opens and repo.Head.FriendlyName can be read without the DLL-load error.

Written by the indexing model from the issue text.

Description

I'm developing a Visual Studio 2022 extension that uses LibGit2Sharp to retrieve Git repository information (such as the current branch name) and to manage open documents based on the active branch. However, when running my extension on Windows, I encounter the following error:

Unable to load DLL 'git2-3f4182d': The specified module could not be found. (Exception from HRESULT: 0x8007007E)

I noticed that the LibGit2Sharp.dll.config file only contains dllmap entries for Linux and macOS, with no mapping for Windows. Despite installing the LibGit2Sharp.NativeBinaries package and verifying that the project’s platform configuration (x86 vs x64) matches the deployed binaries, the error persists.

I'm running on .net 4.7.2. The code is pretty simple since it's an R&D POC.


string testDir = "";
try
{
    using (var repo = new Repository(_repoPath))
    {
        testDir = repo.Head?.FriendlyName;
    }
}

_repoPath is not empty, and it exists as the current Git repository. (with an .git folder)

Dominant language
C#
Stars
3.5k
Forks
925
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from libgit2/libgit2sharp

All issues in libgit2/libgit2sharp

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.