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
First, thanks for dotnet-outdated β it's the engine behind what we built.
We've published dotnet outdated GUI, a JetBrains Rider tool-window that wraps your CLI: it lists a solution's NuGet packages, checks for updates (colored by SemVer severity), and upgrades the ones you pick β in place. It leans specifically on the things your CLI already gets right: Central Package Management (Directory.Packages.props) and NuGet version ranges / floating versions.
It shells out to your tool and surfaces its results β full credit to you for the hard part. It's an independent, unofficial project; no affiliation implied.
How you could help, if you're open to it:
A mention of IDE/GUI integrations in your README so Rider users can find it.
Any feedback on how we invoke the CLI, or behaviors/flags we should rely on vs. avoid across versions.
A heads-up on breaking CLI changes so we can keep the GUI in sync.
Either way β thanks for maintaining such a useful tool. π
Hi @dotnet-outdated maintainers π
First, thanks for
dotnet-outdatedβ it's the engine behind what we built.We've published dotnet outdated GUI, a JetBrains Rider tool-window that wraps your CLI: it lists a solution's NuGet packages, checks for updates (colored by SemVer severity), and upgrades the ones you pick β in place. It leans specifically on the things your CLI already gets right: Central Package Management (
Directory.Packages.props) and NuGet version ranges / floating versions.It shells out to your tool and surfaces its results β full credit to you for the hard part. It's an independent, unofficial project; no affiliation implied.
How you could help, if you're open to it:
Either way β thanks for maintaining such a useful tool. π