-
-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Versions after v3.3.37 doesn't work on Windows 7 #615
Comments
Would you be willing to test the fix, which you can download from the build artifact in #616's PR build? |
I guess that invitation was a bit premature. The PR build failed. I'll work on it. |
First, thanks for answering so quickly. I'll gladly test it when it is ready! |
Worked first try, added it as a local NuGet package for same Console project and made sure it was being used:
Amazing, thanks! |
Thanks for verifying! |
* Switch from PInvoke nuget dependency to CsWin32 Fixes #615 * Update CsWin32 to fix `dotnet build` * Remove dotnet/pinvoke from 3rd party licenses file * include 5E and DA values in zlib header check * ditch linq for exception * Add new NuGet signing certificate See https://devblogs.microsoft.com/nuget/the-nuget-org-repository-signing-certificate-will-be-updated-as-soon-as-march-15th-2021/ for more details * Bump libgit2sharp to 0.27.0-preview-0102 * Run 32-bit tests * GitPack: Don't use MemoryMappedFiles in 32-bit processes * Make sure Streams are disposed of. * Fix bugs with > 2 GB pack files * Apply suggestions from code review Co-authored-by: Andrew Arnott <[email protected]> * Apply `is null` pattern and analyzer Co-authored-by: rhodosaur <[email protected]> Co-authored-by: Frederik Carlier <[email protected]> Co-authored-by: Filip Navara <[email protected]>
With version after v3.3.37, NBGV fails when doing a simple dotnet build in new repo.
Error is as follows:
For full error, see last step.
Running command
ver
on my machineSteps to reproduce
The text was updated successfully, but these errors were encountered: