Open OzBob opened 7 months ago
I think support for .NET Core 2.1 was removed in v14?
Thanks for the update. As there will be more sdk versions slowly go out of support as the years crawl by, do you think it would be a good feature to trap this specific error and report it in a more friendly way or even auto update the .nswag file?
It sounds like something where it'd be nicer if NSwagStudio would either read the old runtime and then tell you it's obsolete or default to the current version for unknown values, but I don't know what ramifications that might have for the command line tools.
Is there anyway to stop NswagStudio from upgrading from a version 13.x? We cannot get off of .Net Core 2.1 atm, and every day after uninstalling 14.x and reinstalling 13.x, NswagStudio has auto updated itself to 14.x again.
Is there anyway to stop NswagStudio from upgrading from a version 13.x? We cannot get off of .Net Core 2.1 atm, and every day after uninstalling 14.x and reinstalling 13.x, NswagStudio has auto updated itself to 14.x again.
Sorry to add insult to the injury, but NSwagStudio automatic updates are probably least of your problems if you're still on NET 2.1 😉
Upgraded to v14 from v13 now opening a .nswag file like:
get the following error:
when run
dotnet --list-runtimes
getwhen run
dotnet --list-sdks
getI'll change the definition manually to Net60, but FYI - there maybe regression tests for you to run.