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.

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

Adding a route to a Blazor component doesn't work with hot reload #52582

Open
danroth27 opened this issue Dec 5, 2023 · 2 comments
Open

Adding a route to a Blazor component doesn't work with hot reload #52582

danroth27 opened this issue Dec 5, 2023 · 2 comments
Labels
area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-hot-reload This issue is related to the Hot Reload feaature Pillar: Dev Experience Priority:1 Work that is critical for the release, but we could probably ship without triaged

Comments

@danroth27
Copy link
Member

Repro steps:

  • Create a new Blazor Web App with the default options
  • Run the app
  • In Counter.razor add @page "/counter2"
  • Apply the change to the running app using hot reload
  • Try to browse to /counter2

Expected result: The Counter component renders when browsing to /counter2
Actual result: Browsing to /counter2 results in a 404
Workaround: Manually restart the app

@dotnet-issue-labeler dotnet-issue-labeler bot added the area-blazor Includes: Blazor, Razor Components label Dec 5, 2023
@danroth27 danroth27 added the feature-hot-reload This issue is related to the Hot Reload feaature label Dec 5, 2023
@surayya-MS surayya-MS added this to the .NET 9 Planning milestone Dec 6, 2023
@ghost
Copy link

ghost commented Dec 6, 2023

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@ghost
Copy link

ghost commented Dec 15, 2023

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@mkArtakMSFT mkArtakMSFT added enhancement This issue represents an ask for new feature or an enhancement to an existing one triaged labels Dec 15, 2023
@mkArtakMSFT mkArtakMSFT added the Priority:1 Work that is critical for the release, but we could probably ship without label Jan 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-hot-reload This issue is related to the Hot Reload feaature Pillar: Dev Experience Priority:1 Work that is critical for the release, but we could probably ship without triaged
Projects
None yet
Development

No branches or pull requests

4 participants
@danroth27 @mkArtakMSFT @surayya-MS and others