Repository navigation
DotUninstall, a cross platform UI version of this tool #410
Description
I built a minimalist UI for this tool using Uno a few weeks ago, and after a few iterations it is now mature enough to be announced here for more audience.
It relies on the same detection/uninstall logic from this repo (inherited via submodule), but also enriches the display by pulling down .NET metadata from builds.dotnet.microsoft.com. Through quick links to release notes, support policies, etc., developers can get a better understanding of what bits they installed.
Activity
lextm commentedon Dec 19, 2025
@marcpopMSFT Would there be any transparency on how an external tool like DotUninstall might sync up with the Microsoft internal testing tags? Multiple places (#341 #419 #345) a recent build 1.7.660902 were mentioned but that tag isn't visible from the public tag list. You can see the intervals between public tags are rather long (which makes little sense).
marcpopMSFT commentedon Jan 7, 2026
We create public tags whenever we do releases and that is quite infrequent. We were not investing in this tool for a couple of years other than updating its version support. We've done some additional investments the past couple of years to handle arm64 support and mac signing as those were critical changes to the ecosystem we'd been slow to respond to. Even then, we collected changes together and released them all at once.
If an issue references a version that's not a tag, that means that's a version in prerelease. We're currently testing a release that adds windows desktop support and migration to WiX 5. That will release this month (once we have signoff) but I don't have an exact date and I'll create a tag at that time.
So in short, the tag list should match our release list and can be used.
lextm commentedon Jan 7, 2026
Thanks. That already covers what I asked for. I will monitor new tags and update DotUninstall accordingly.