If the parameter is set LD_DEBUGto allor files, we get similar results

[suchona.kani.z]

First, we should take a closer look at the returned error message to understand the root problem. Only then we take further action and analyze code from the open source repository libgit2 .


We know that the library is a wrapper around the C implementation of libgit2 to be able to use it in the managed world of .NET. With this background knowledge, we can assume that the reference to is git2-106a5f2to System.DllNotFoundExceptionthe native library. The next step is to determine where the library is being loaded from and where the error occurs. With this information, it is easier to understand the problem.

Investigating with debug options
The error message gives us all the information we need to proceed. It indicates lebanon consumer email list that LD_DEBUGis being used. So let's look at the output with this environment variable (output greatly abbreviated):






If no specific version is applied to the shared object file, I think the file should be system-sourced. We check the package manager and install the latest version of the underlying library libgit2on the system.



But even after installing and updating, the error still occurs. As suspected, there is nothing related to the global installation of the library. It should be shipped with the NuGet package.

So the next step is to investigate the issues on GitHub and find a possible solution.

Investigate GitHub bugs for possible solutions
Before analyzing the installation scripts or library code, we examine the bugs on GitHub.Some issues indicate that the correct dependency of the package should be used. This is LibGit2Sharp.NativeBinariesin version 2.0.306. This was already the case when the file sobj/project.assets.jsonwas checked. However, several issues indicate that there are problems with .Net 5 that should be fixed in the preview version 0.27.0 of the NuGet package LibGit2Sharp.

Install the preview version of the library
Let's update the package reference now to see if the preview version .Net-6-Anwendungfixes the issue for you.


The submodule works as expected, as it does with the preview version of the NuGet package. The submodule suffers from similar drawbacks as using a package manager: the reference must be manually updated when a new version is released.

When the submodule is used, the masterbranch can be checked out directly and checked for the latest development version. Most importantly, when a stable release of 0.27.0the package is released, this option must be re-evaluated.

Conclusion
To see all the changes made since the last released version, we can check out the diff on GitHub v0.26..master directly.

The help for submodules is extensive. It can be accessed at man 1 git-submoduleand man 7 gitsubmodules.

For my project, I chose the submodule workaround because it has several advantages:

By creating it regularly, I can monitor the submodule for updates.
I stay updated on changes to the library.
I can provide feedback to the library developers because I am working on a version that includes new features and bug fixes.
I can test different versions of the library on different branches.
Would you like to find out more about other exciting topics from the adesso world? Then take a look at our previously published blog posts .

Image Vincent Scherb
author Vincent Scherb

Vincent Scherb is a software developer at adesso in Nuremberg. He works primarily as a backend developer in the manufacturing industry using Microsoft technologies.

Would you like to receive our adesso blogging update regularly? Then simply subscribe to our newsletter and you will receive the latest posts from our tech blog conveniently by email.