Open pjcollins opened 1 year ago
A parameter to ignore the 'safe' limits might be interesting - really we have a roughly-yearly process of bumping this allowed upper limit ourselves. @joeloff might be time to do so again for 8.0?
Quick comment that this issue still persists for the latest release
Found this issue after getting an error while trying to uninstall .Net 8 RC 1 (8.0.100-rc.1.23463.5) after the RC2 release.
It would be good to add support for .NET 8 previews. My machines start to get polluted by preview bits.
I think this should be fixed for .NET 8 with https://github.com/dotnet/cli-lab/pull/268.
I also took an initial stab at allowing the upper version to be ignored for future versions in https://github.com/dotnet/cli-lab/pull/269, though this still needs some tests.
Any updates on .NET 8 support?
Apologies, to nag but... Any updates on .NET 8 support?
What's holding this back? Can we help?
See also issues #273 and #276
We have some scenarios where it could be useful to uninstall .NET previews from the latest band (currently 8.0) as we move from preview to preview, however this does not appear to be supported:
I am trying to better understand this restriction. Is this not allowed because the latest SDK can have a lot of churn in between previews and the behavior of the tool may be unreliable?
Would be reasonable to add a command line param that would let users ignore this upper limit? https://github.com/dotnet/cli-lab/blob/0eab6c3a145e91f1ce16043ec63d9dfe2ac702ea/src/dotnet-core-uninstall/Shared/VSVersioning/VisualStudioSafeVersionsExtractor.cs#L16