Skip to content

Conversation

@tmat
Copy link
Member

@tmat tmat commented Jan 21, 2025

Ports #46112 to 2xx.

Context

dotnet-watch does not set environment variables correctly causing browser refresh to stop working after restarting a web project due to rude edit. The issue only occurs in Aspire orchestrated web projects, not in standalone web projects.

Customer impact

Web pages are not refreshed when further changes are made to the web project, after restarting due to rude edit, which greatly diminishes the value of Hot Reload.

Changes made

Apply the necessary environment variables to the restarted process.

Testing

Manual testing to confirm that the changes fix the issue.

Risks

Negligible. The fix is simple.

@ghost ghost added Area-AspNetCore RazorSDK, BlazorWebAssemblySDK, dotnet-watch untriaged Request triage from a team member labels Jan 21, 2025
@dotnet-policy-service
Copy link
Contributor

Thanks for your PR, @tmat.
To learn about the PR process and branching schedule of this repo, please take a look at the SDK PR Guide.

@tmat tmat added Servicing-consider Area-Watch and removed Area-AspNetCore RazorSDK, BlazorWebAssemblySDK, dotnet-watch labels Jan 21, 2025
@tmat
Copy link
Member Author

tmat commented Jan 21, 2025

@phil-allen-msft ptal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-Watch Servicing-approved untriaged Request triage from a team member

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants