Extract default ASP.NET port from launch setting profile #222
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Starting with .NET 6, new ASP.NET applications are scaffolded to use a dynamically generated port, rather than
5000used by earlier frameworks. This change updates our default port logic to sniff thelaunchSettings.json, extracting the application URL for the "project" profile (i.e. the profile used by the Kestrel host, which is also now the default for ASP.NET applications), and using its port number as the default provided to the user. (The user can, of course, overwrite that value with their own.)Resolves #214.