Skip to content

Cover dotnet-serve local testing for Blazor WASM#37010

Merged
guardrex merged 6 commits intomainfrom
guardrex-patch-3
Apr 16, 2026
Merged

Cover dotnet-serve local testing for Blazor WASM#37010
guardrex merged 6 commits intomainfrom
guardrex-patch-3

Conversation

@guardrex
Copy link
Copy Markdown
Collaborator

@guardrex guardrex commented Apr 15, 2026

Fixes #37009

Wade, Tom ... Just need one review on this one. I've used Nate's HTTP server several times with great success. I think it should be called out to readers. He's maintaining it ... natemcmaster/dotnet-serve#43.

cc: @natemcmaster


Internal previews

📄 File 🔗 Preview link
aspnetcore/blazor/host-and-deploy/webassembly/index.md aspnetcore/blazor/host-and-deploy/webassembly/index

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds guidance to the Blazor WebAssembly hosting/deployment article for serving a published app locally using dotnet-serve as a simple HTTP server option.

Changes:

  • Adds a new “Serve a Blazor WebAssembly app locally for testing” section.
  • Links to natemcmaster/dotnet-serve and includes a third-party tool warning.

Comment thread aspnetcore/blazor/host-and-deploy/webassembly/index.md Outdated
Comment thread aspnetcore/blazor/host-and-deploy/webassembly/index.md
Comment thread aspnetcore/blazor/host-and-deploy/webassembly/index.md Outdated
dotnet-serve` .NET tool](https://github.com/natemcmaster/dotnet-serve).

> [!WARNING]
> The [`natemcmaster/dotnet-serve` .NET tool](https://github.com/natemcmaster/dotnet-serve) isn't owned or maintained by Microsoft and isn't covered by any Microsoft Support Agreement or license. Use caution when using a third-party tool, especially for testing security scenarios. Confirm that the tool follows official specifications and adopts security best practices. Keep the tool's version current to obtain the latest bug fixes.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we just roll the command into the official SDK? I built the tool like 10 years ago to demo global tool capabilities, but seems like a generally useful thing to build in.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ping @danroth27

guardrex and others added 2 commits April 15, 2026 16:15
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Corrected the hyphenation in the phrase 'open-source and commercial' for consistency.
Copy link
Copy Markdown
Contributor

@wadepickett wadepickett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved. Looks good. (The remaining question of rolling the command into the official SDK would be an issue filed on the product code, and would not effect this PR, although depending on the outcome may require a new PR on the doc later.)

@guardrex
Copy link
Copy Markdown
Collaborator Author

@natemcmaster @danroth27 ... I'll be 👂 for news on the tool becoming part of the SDK. I'll open an issue and remove the 3rd party remarks if that comes to pass. If you think to let me know about it later, give me a holler 📣 .

@guardrex guardrex removed the request for review from tdykstra April 16, 2026 17:08
@guardrex guardrex merged commit c066e68 into main Apr 16, 2026
3 of 4 checks passed
@guardrex guardrex deleted the guardrex-patch-3 branch April 16, 2026 17:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remark and link Nate McMaster's dotnet serve tool for Blazor WASM

4 participants