Skip to content

Blazor project creation: Default$b.interval in bootstrap.bundle.js is being set to the port number #48811

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.

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

Open
rough-street opened this issue May 5, 2025 · 1 comment
Assignees
Labels
Area-AspNetCore RazorSDK, BlazorWebAssemblySDK, dotnet-watch untriaged Request triage from a team member

Comments

@rough-street
Copy link

Describe the bug

When I create a new blazorwasm standalone app and look at the generated files, I see that the value of Default$b.interval in projectname/wwwroot/lib/bootstrap/dist/js/bootstrap.bundle.js:1131 has been set to the same value as the port in the url set in projectname/Properties/launchSettings.json:9 at "profiles"->"http"->"applicationUrl"

This is not just a coincedence - when another project is created and is automatically given a different port number in launchSettings.json, again Default$b.interval is assigned this new port number.

To Reproduce

Run dotnet new blazorwasm -o projectname on Linux (I haven't tried Windows).
Examine the above files and see that values match.
Delete the project and recreate.
Note that the port number at projectname/Properties/launchSettings.json:9 is now different (fine) and that the Default$b.interval now is assigned the new port number.

Exceptions (if any)

None

Further technical details

Output of dotnet --info

.NET SDK:
Version: 9.0.104
Commit: 7931ad4860
Workload version: 9.0.100-manifests.dc2cb94f
MSBuild version: 17.12.27+7931ad486

Runtime Environment:
OS Name: ubuntu
OS Version: 22.04
OS Platform: Linux
RID: ubuntu.22.04-x64
Base Path: /usr/lib/dotnet/sdk/9.0.104/

.NET workloads installed:
[wasm-tools]
Installation Source: SDK 9.0.100
Manifest Version: 9.0.3/9.0.100
Manifest Path: /usr/lib/dotnet/sdk-manifests/9.0.100/microsoft.net.workload.mono.toolchain.current/9.0.3/WorkloadManifest.json
Install Type: FileBased

Configured to use loose manifests when installing new manifests.

Host:
Version: 9.0.3
Architecture: x64
Commit: 7931ad4860

.NET SDKs installed:
8.0.115 [/usr/lib/dotnet/sdk]
9.0.104 [/usr/lib/dotnet/sdk]

.NET runtimes installed:
Microsoft.AspNetCore.App 8.0.15 [/usr/lib/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 9.0.3 [/usr/lib/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 8.0.15 [/usr/lib/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 9.0.3 [/usr/lib/dotnet/shared/Microsoft.NETCore.App]

Other architectures found:
None

Environment variables:
Not set

global.json file:
Not found

Learn more:
https://aka.ms/dotnet/info

Download .NET:
https://aka.ms/dotnet/download

@dotnet-policy-service dotnet-policy-service bot added the untriaged Request triage from a team member label May 5, 2025
@Forgind Forgind added the Area-AspNetCore RazorSDK, BlazorWebAssemblySDK, dotnet-watch label May 6, 2025
@Forgind
Copy link
Contributor

Forgind commented May 6, 2025

Rerouting to @dotnet/aspnet-blazor-eng for triage

@Forgind Forgind removed their assignment May 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-AspNetCore RazorSDK, BlazorWebAssemblySDK, dotnet-watch untriaged Request triage from a team member
Projects
None yet
Development

No branches or pull requests

3 participants