-
Notifications
You must be signed in to change notification settings - Fork 2
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
Hot reload not working when running in ASP.NET Core hosted mode #5
Comments
Update: I assumed With I'll keep an eye on any changes in behavior as i do my tweaks to the hosted template and compare that to the blazorwasm single-project.
|
I also did a lot of searching around and from what I read, hosted mode just doesn't work at all with hot reload so it's not really related to your tailwind integration. As a workaround I am just launching the two hosts separately on separate ports, one for the UI and one for the API. After that, hot reloading does work. It's just a bit annoying. I think with later versions of hot reload this might get improved. Though if you find a way to make it work that would be great and please reply in this thread about it. |
I was integrating a TailBlazor WASM template into my application. Noticed hot reload wasnt working when I launch it from a .Net Core hosted project that also contains the REST API. Only when I run the individual TailBlazor project does hot reload work.
The text was updated successfully, but these errors were encountered: