Solution-Level or Repo-Level Lock Files
### NuGet Product(s) Involved Other/NA ### The Elevator Pitch Managing multiple project lock files for a huge solution or a repo can be daunting. This was even called out in 2018 when lock files were introduced: https://devblogs.microsoft.com/nuget/enable-repeatable-package-restores-using-a-lock-file/#solution-or-repo-lock-file Has there been any further thought or development on solution-level or repository-level lock files? The link in those paragraphs doesn't contain any further information on centralised lock files, only on centralised versioning, and I can't find any related issues here on GitHub either. ### Additional Context and Details This is particularly important to me as I don't want to have to go and update approx. 1000 csproj files when updating a core package such as a Roslyn Analyzers package, or Newtonsoft.Json, or similar. This also gets much more difficult when multiple developers are trying to make changes (e.g. adding a ProjectReference which adds new transitive NuGet dependencies, which I believe requires updating the lock file?), and looks like it will quite quickly lead to merge conflict hell. In many of our projects already use [Paket](http://github.com/fsprojects/Paket), which provides a single top-level lock file for all dependencies defined in a `paket.dependencies` file (analogous to `nuget.config` + `Directory.Packages.props`). This makes batch operations such as upgrading or downgrading a package across an entire repo a fairly easy and
Posted by yaakov-h on Feb 6, 2023, 7:20 AM
Tags
Related issues
- This is the biggest problem with contracts, there's simply no way to actually say "please always execute this check".
- I don't disagree with you on this, I worked my whole life in corporate and haven't worked as a OSS maintainer before, though I will _and ...
- the new VSCode UI, looks cute, i don't like it.
- I've been working on my own private harness for the past 8 months, and I've been collecting ideas from such repos I've stumbled upon.
- The way AI is able to interact with outside resources is pretty impressive, but the quality of code it produces to me is still questionab...
- Add PR-style review comments in Git Diff UI that feed into the active agent thread
Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments
ux (Software)
This is the biggest problem with contracts, there's simply no way to actually say "please always execute this check".
I don't disagree with you on this, I worked my whole life in corporate and haven't worked as a OSS maintainer before, though I will _and ...
the new VSCode UI, looks cute, i don't like it.
I've been working on my own private harness for the past 8 months, and I've been collecting ideas from such repos I've stumbled upon.
The way AI is able to interact with outside resources is pretty impressive, but the quality of code it produces to me is still questionab...
Add PR-style review comments in Git Diff UI that feed into the active agent thread
Thanks for indulging me so far, by the way, I really appreciate this discussion, it's very stimulating.
Migrate GDScript to the GDExtension mechanism and overhaul the implementation
Solution-Level or Repo-Level Lock Files
### NuGet Product(s) Involved Other/NA ### The Elevator Pitch Managing multiple project lock files for a huge solution or a repo can be daunting. This was even called out in 2018 when lock files were introduced: https://devblogs.microsoft.com/nuget/enable-repeatable-package-restores-using-a-lock-file/#solution-or-repo-lock-file Has there been any further thought or development on solution-level or repository-level lock files? The link in those paragraphs doesn't contain any further information on centralised lock files, only on centralised versioning, and I can't find any related issues here on GitHub either. ### Additional Context and Details This is particularly important to me as I don't want to have to go and update approx. 1000 csproj files when updating a core package such as a Roslyn Analyzers package, or Newtonsoft.Json, or similar. This also gets much more difficult when multiple developers are trying to make changes (e.g. adding a ProjectReference which adds new transitive NuGet dependencies, which I believe requires updating the lock file?), and looks like it will quite quickly lead to merge conflict hell. In many of our projects already use [Paket](http://github.com/fsprojects/Paket), which provides a single top-level lock file for all dependencies defined in a `paket.dependencies` file (analogous to `nuget.config` + `Directory.Packages.props`). This makes batch operations such as upgrading or downgrading a package across an entire repo a fairly easy and
Comments (0)
No comments yet. Start the discussion.