Fix Blazor template HTTPS profile to include HTTP URL #62853
Merged
Conversation
This file contains hidden or 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
Co-authored-by: javiercn <[email protected]>
Copilot
AI
changed the title
Copilot finished work on behalf of
javiercn
July 22, 2025 09:06
There was a problem hiding this comment.
Pull Request Overview
This PR fixes an inconsistency in the Blazor Web template's HTTPS launch profile by adding the HTTP URL to the applicationUrl configuration. The change ensures consistency with other ASP.NET Core project templates.
Key Changes
- Updated the HTTPS profile's applicationUrl to include both HTTPS and HTTP URLs
- Maintained consistency with other ASP.NET Core templates that use the same pattern
DamianEdwards
approved these changes
Jul 30, 2025
|
/backport to release/10.0-preview7 |
|
Started backporting to release/10.0-preview7: https://github.com/dotnet/aspnetcore/actions/runs/16631436102 |
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.
The Blazor Web template's HTTPS launch profile was missing the HTTP URL in its
applicationUrlconfiguration, making it inconsistent with other ASP.NET Core templates.Problem:
In
src/ProjectTemplates/Web.ProjectTemplates/content/BlazorWeb-CSharp/BlazorWebCSharp.1/Properties/launchSettings.json, the HTTPS profile only had:Solution:
Updated to include both HTTPS and HTTP URLs for consistency:
This matches the pattern used by all other ASP.NET Core templates:
"applicationUrl": "https://localhost:5001;http://localhost:5000""applicationUrl": "https://localhost:5001;http://localhost:5000""applicationUrl": "https://localhost:5001;http://localhost:5000""applicationUrl": "https://localhost:5001;http://localhost:5000"The LocalhostTld conditional branch was already correct and included both URLs.
Fixes #62852.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.