You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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:
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.
_repoPath is not empty, and it exists as the current Git repository. (with an .git folder)
The text was updated successfully, but these errors were encountered: