Brandon Ording

Unfortunately, I would have to say it's more on the dead side of things at this point. I'm the last person who's paying any attention to the repo, and it's...

libgit2 already supports OpenSSL 3, and we test against Ubuntu 22.04 in the LibGit2Sharp repo, and everything works fine. I've also done some extra manual testing recently, and haven't been...

@johnbailey-transactcampus You really shouldn't need to do that. It works just fine with OpenSSL 3. I have tests that run against OpenSSL 3 that prove that. If you can provide...

> LibGit2Sharp NuGet package ([0.20.0-preview-0175](https://www.nuget.org/packages/LibGit2Sharp/0.27.0-preview-0175)) That version is old and out of date. You should definitely update to the latest version and then see if you still have the problem....

Hmm, how do you see this working? I wouldn't think we'd want to move to always packaging the Debug version only. Most of the time I'd think people would want...

Maybe some sort of NativeBinaries.Debug package that's built in addition to the regular package? Then LibGit2Sharp could depend on the Debug package, and when building the LibGit2Sharp package, it could...

Why did this release include the 8.0.300 SDK but the matching Visual Studio 17.9.7 update shipped with 8.0.205? If I install 8.0.300 manually, it doesn't work properly in Visual Studio...

I did take a look at this a bit this weekend, and I'm not sure that the issue is solely a `DllImport` vs. `LibraryImport` thing. There is enough evidence around...

Found a couple more issues on the dotnet repo that likely explain a bit more what's going on here. Currently it looks like warnings for AOT-problematic P/Invokes via `DllImport` are...

> What would we need to do on the libgit2 side? I'm just theorizing here, but if it turns out there was a libgit2 API pattern that there was no...