Terminal would benefit from having a single canonical version number for each of its NuGet dependencies #17016

Closed
opened 2026-01-31 05:29:56 +00:00 by claunia · 0 comments
Owner

Originally created by @dmachaj on GitHub (Mar 16, 2022).

Description of the new feature/enhancement

Currently there are packages.config files in lots of directories, with those same projects referencing props/targets from packages/ with a version string in the path. This is frustrating because version changes or new dependencies require updating lots and lots of build files identically. There is also the possibility of error where locations are missed.

Proposed technical implementation details (optional)

Consolidate to a single packages.config and a common props/targets file that has the detailed version numbers in it. All projects include those. When a version needs to be updated only that set of files need to be modified, not dozens.

Originally created by @dmachaj on GitHub (Mar 16, 2022). # Description of the new feature/enhancement Currently there are packages.config files in lots of directories, with those same projects referencing props/targets from packages/ with a version string in the path. This is frustrating because version changes or new dependencies require updating lots and lots of build files identically. There is also the possibility of error where locations are missed. # Proposed technical implementation details (optional) Consolidate to a single packages.config and a common props/targets file that has the detailed version numbers in it. All projects include those. When a version needs to be updated only that set of files need to be modified, not dozens.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#17016