-
-
Notifications
You must be signed in to change notification settings - Fork 84
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
Proposal: support NuGet Central Package Management lock files #444
Comments
When working on this this we definitely took this as first direction. Unfortunately the hash in the NuGet lockfile turned out differ from the file hash of the downloaded nupkg which made it incompatible with Bazel's download logic. If this has changed now I'm keen to implement this. |
Glade to learn the background! Should we file a proposal to NuGet to support this kind of hash? |
I see a discussion about NuGet support single lock file may also helps to us. NuGet/Home#12409 |
Hi @tomdegoede , It will be greatfull to get any updates about the feature!
Our solution need the feature. We have 100+ projects. Thanks in advance. |
@romaromaniv you can leverage the custom lockfile format. NuGet lock files are not compatible and only work per project. |
@tomdegoede thanks for the quick reply. Could you please provide some more details - what means "the custom lockfile format"? |
This issue proposed the NuGet lockfile, but bazel_dotnet uses its own format. Please look at the examples. |
NuGet Central Package Management can generate lock files, see Enable repeatable package restores using a lock file.
Considered the well integration with Visual Studio and broadly adoption, I propose our rules_dotnet support NuGet.
The text was updated successfully, but these errors were encountered: