You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Epic]: Tooling support for central package management #9015
Reacted by Sean G. Wright, Varorbc, Tobias Tengler, Nirmal Guru, xamadev, Stuart Lang, Conan the Dev, Per Olav Flaten, Andreas Falkner, Thomas Gossler and 11 more
changed the title [-][Centrally managing NuGet packages and versions] Visual Studio integration (MVP scenarios)[/-][+][Feature]: Visual Studio integration when using central package management[/+]on May 23, 2022
changed the title [-][Feature]: Visual Studio integration when using central package management[/-][+][Epic]: Visual Studio integration when using central package management[/+]on May 23, 2022
changed the title [-][Epic]: Visual Studio integration when using central package management[/-][+][Epic]: Tooling support for central package management[/+]on Aug 18, 2022
Sometimes after updating packages via the Visual Studio NuGet UI my Directory.Packages.props file will not contain updated version numbers in the relevant <PackageVersion> lines, but instead contain new <PackageVersion Update...> lines. I don't know yet how to reproduce this bug. I'll create an issue once I know.
Activity
[-][Centrally managing NuGet packages and versions] Visual Studio integration (MVP scenarios)[/-][+][Feature]: Visual Studio integration when using central package management[/+][-][Feature]: Visual Studio integration when using central package management[/-][+][Epic]: Visual Studio integration when using central package management[/+][-][Epic]: Visual Studio integration when using central package management[/-][+][Epic]: Tooling support for central package management[/+]andrew-hampton commentedon Sep 22, 2022
@jeffkl is there a target release for these tooling updates?
14 remaining items
cremor commentedon May 9, 2023
Directory.Packages.propsfile will not contain updated version numbers in the relevant<PackageVersion>lines, but instead contain new<PackageVersion Update...>lines. I don't know yet how to reproduce this bug. I'll create an issue once I know.Directory.Packages.propsoverwrites the version range with the specific new version. This is point 2 of Respect upper bounds of Version Range when updating in UI, PMC and dotnet package update #6566, so this also affects CPM.Templates create compile errors in solutions with Central Package Management (CPM) dotnet/aspnetcore#48569
Templates create compile errors in solutions with Central Package Management (CPM) dotnet/sdk#48903
Add support for batch "Add a reference to a project file" invocation #12629
martinrrm commentedon May 22, 2023
@cremor 1. I saw that behavior in the past one time and wasn't able to repro it since, I'll test it again but not sure what can cause that bug.
cremor commentedon May 22, 2023
About point 2:
Directory.Packages.propscontains a version range likeVersion="[1.0.0, 2.0.0)".I don't see anything "disabled in the PM UI" here.
Directory.Packages.propsfile to1.1.0(bad - upper bound is gone).IanKemp commentedon Jul 12, 2023
@martinrrm please can you do this?