dotnet API backend webservice in tutorial is written in EOL .Net7, should be dotnet .Net8? #113
Description
This issue is for a: (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [x] regression (a behavior that used to work and stopped in a new release)
Minimal steps to reproduce
On a mac in Visual Studio Code, do the normal things to get C#/.Net running locally. You'll see that only 6 and 8 are offered, so take a gander at either and launch the project per the tutorial dotnet run.
Any log messages given by the failure
✗ dotnet run
You must install or update .NET to run this application.
App: /Users/bronius/projects/sandbox/ms-identity-ciam-javascript-tutorial/2-Authorization/2-call-api-angular/API/ToDoListAPI/bin/Debug/net7.0/ToDoListAPI
Architecture: arm64
Framework: 'Microsoft.AspNetCore.App', version '7.0.0' (arm64)
.NET location: /usr/local/share/dotnet
The following frameworks were found:
6.0.33 at [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
8.0.8 at [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Learn more:
https://aka.ms/dotnet/app-launch-failed
To install missing framework, download:
https://aka.ms/dotnet-core-applaunch?framework=Microsoft.AspNetCore.App&framework_version=7.0.0&arch=arm64&rid=osx-arm64&os=osx.14
Expected/desired behavior
At launch, the terminal should look more like:
✗ dotnet run
info: Microsoft.Hosting.Lifetime[14]
Now listening on: https://localhost:44351
info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Development
info: Microsoft.Hosting.Lifetime[0]
Content root path: /Users/bronius/projects/sandbox/ms-identity-ciam-javascript-tutorial/2-Authorization/2-call-api-angular/API/ToDoListAPI
(Note, you may want to also have run dotnet dev-certs https --trust per https://learn.microsoft.com/en-us/aspnet/core/security/enforcing-ssl)
OS and Version?
macOS Sonoma 14.7
Versions
As of commit #15ca3b44a Thu Aug 15 17:34:52 2024 +0100
Mention any other details that might be useful
Appears that upgrading the codebase to support .Net framework 8.x does the trick. I'll attach a patch in my next comment.