Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The launchSettings.json in an ASP.NET Core hosted Blazor WebAssembly app isn't generated correctly #18612

Closed
danroth27 opened this issue Jan 28, 2020 · 0 comments · Fixed by #18842
Closed

The launchSettings.json in an ASP.NET Core hosted Blazor WebAssembly app isn't generated correctly #18612

danroth27 opened this issue Jan 28, 2020 · 0 comments · Fixed by #18842
Assignees
@mkArtakMSFT
Labels
area-blazor Includes: Blazor, Razor Components bug This issue describes a behavior which is not expected - a bug. Done This issue has been fixed feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly
Milestone
blazor-wasm-3.2-p...

Comments

@danroth27
Copy link
Member

The generated launchSettings.json file in a Blazor WebAssembly template isn't generated with the correct ports and profile name. It looks like there's some sort of template authoring issue that's preventing the appropriate template substitutions from taking place.

The ports are always 8080 and 5000, when they should be generated randomly by VS.

The name of the project profile is always "Company.WebApplication1" when it should pick up the name of the created project.
@danroth27 danroth27 added area-blazor Includes: Blazor, Razor Components feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly labels Jan 28, 2020
@mkArtakMSFT mkArtakMSFT added this to the blazor-wasm-3.2-preview2 milestone Jan 28, 2020
@mkArtakMSFT mkArtakMSFT self-assigned this Jan 28, 2020
@mkArtakMSFT mkArtakMSFT added the bug This issue describes a behavior which is not expected - a bug. label Jan 28, 2020
@mkArtakMSFT mkArtakMSFT mentioned this issue Feb 6, 2020
Merged
@mkArtakMSFT mkArtakMSFT linked a pull request Feb 6, 2020 that will close this issue
Auto-generate random port for the server project #18842
Merged
@mkArtakMSFT mkArtakMSFT added Done This issue has been fixed and removed Working labels Feb 9, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Mar 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@mkArtakMSFT mkArtakMSFT

Labels
area-blazor Includes: Blazor, Razor Components bug This issue describes a behavior which is not expected - a bug. Done This issue has been fixed feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly
Projects
None yet
Milestone
blazor-wasm-3.2-preview2
Development

Successfully merging a pull request may close this issue.

Auto-generate random port for the server project dotnet/aspnetcore
2 participants
@danroth27 @mkArtakMSFT