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
Please be sure to check the existing issues (both open and closed!).
Issue description
The way the sample app is created now is somewhat confusing.
launchsettings.json only has http://localhost:5000 - I would expect it to also contain https://localhost:5001
Program is using .UseCloudHosting(<PORTNUMBER>), I would at least expect this to have .UseCloudHosting(<PORTNUMBER>, <SECUREPORTNUMBER>)
When running locally, without "Urls":"https://localhost:5001" in the appsettings.json the app will not register localhost - suggestion - add this by default to the appsettings.Development.json file.
I would also suggest adding code comments to draw the user's attention to the various moving parts to greater assist with their learning and comprehension.
I would also consider using the minimal hosting pattern for .NET 6 as this is more in line with current MS dotnet new templates.
Please be sure to check the existing issues (both open and closed!).
Issue description
The way the sample app is created now is somewhat confusing.
launchsettings.json only has
http://localhost:5000
- I would expect it to also containhttps://localhost:5001
Program is using
.UseCloudHosting(<PORTNUMBER>)
, I would at least expect this to have.UseCloudHosting(<PORTNUMBER>, <SECUREPORTNUMBER>)
When running locally, without
"Urls":"https://localhost:5001"
in the appsettings.json the app will not register localhost - suggestion - add this by default to theappsettings.Development.json
file.I would also suggest adding code comments to draw the user's attention to the various moving parts to greater assist with their learning and comprehension.
I would also consider using the minimal hosting pattern for .NET 6 as this is more in line with current MS dotnet new templates.
@ccheetham and I discussed the above on a call
The text was updated successfully, but these errors were encountered: