search

dotnet / sdk

Core functionality needed to create .NET Core projects, that is shared between Visual Studio and CLI
https://dot.net/core
MIT License
2.7k stars 1.06k forks source link

Unable to determine whether a package based SDK is outdated #31745

Open RachelDavids opened 1 year ago

RachelDavids commented 1 year ago

The command "dotnet list package --outdated" does not include any checks whether a packaged based SDK could be upgraded. This could also potentially affect any packages consumed and/or imported in that SDK.

Any user consuming any of these packages must manually search specifically for the package and then manually edit the various files which reference any hard-coded version number.

dotnet-issue-labeler[bot] commented 1 year ago

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

KalleOlaviNiemitalo commented 1 year ago

Is this issue about MSBuild project SDKs? I had filed https://github.com/NuGet/Home/issues/10669 but it was moved to https://github.com/dotnet/sdk/issues/16523 and then closed there because it was considered a NuGet issue after all.

RachelDavids commented 1 year ago

@KalleOlaviNiemitalo Appears we both want the same thing and nobody seems to know where this issue should belong

KalleOlaviNiemitalo commented 1 year ago

https://github.com/NuGet/Home/issues/12326 is another issue about dependencies on MSBuild project SDKs. Not a duplicate of this, though.

nagilson commented 1 year ago

Moving to team triage as I hope we can figure out where this change actually needs to go and which change we would want to do. Most everything in list is maintained by nuget but it sounds like they might believe a different change in the sdk would be better.

marcpopMSFT commented 1 year ago

The list package command routes to nuget which doesn't recognize the nuget sdk as a package in the project. This could either be done on the nuget side by including those or potentially done on the sdk side as an extra command that was something like dotnet list sdks

@JonDouglas @dsplaisted as this is a weird one. Do we really want a new command just for sdks when most sdks are not nuget sdks?

JonDouglas commented 1 year ago

@marcpopMSFT should we include more package SDK owners here for their feedback?

Yes, NuGet owns this list area, but we would need to get feedback regarding the right behavior here if that's the desired command to expand this functionality to.

Our list command today is really scoped to PackageReference dependencies, not necessarily package project sdk dependencies used for dev/build. We're ignorant of those today to my knowledge.

This is a good suggestion, thank you for raising it.