-
Notifications
You must be signed in to change notification settings - Fork 10k
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 for ASP.NET Core #18486
Comments
Hi @mkArtakMSFT, Thanks for your great efforts for making Asp.net core more powerful. I was searching for Asp.net Core Hot Reload feature but I have struggled to find any good solution. We are using Flutter hot reload and you can't imagine how this feature makes us productive while prototyping and making new apps. For Asp.net Core we have found watch tool, but it's relay not making us productive because it's not supporting debugging with breakpoints and the state of the server restarts each time we save our changes. What we expect to be able to set breakpoints in our controllers, start the server, add or modify new methods and codes then click save and see the changes when we hit the controllers again without the need to restarting the asp.net app. Is that what you are trying to implement? |
Is there any update on this? This would make is super productive when working on .net core applications. Take a look at https://www.livesharp.net/ |
Thanks for contacting us. |
This comment has been minimized.
This comment has been minimized.
@mkArtakMSFT Can you remove the clickbait comment from Jan 15, please? |
Hello! I want to ask you the same thing as @EmadBustati . If this were implemented, could I change code in my controller (or domain, or any other layer of my application) during development and things would hot reload? Or is only for the API project? My project does not use razor; it's purely an API that returns JSON; would this be supported? |
Here's a community solution that implements hot reloading for Razor which you might want to look at for inspiration: https://github.com/RickStrahl/Westwind.AspnetCore.LiveReload |
According to previous .NET 6 preview release blogs, I think the answer is YES. |
Does this include Hot Reload for ASP.NET Core inside a docker container? |
Hot reload builds my project, and then again, and then again, etc... Is there a hotfix available? Am I the only one? This does not happen all the time, but once it does, I can't seem to fix it |
@PeterHimschoot could you please file a separate issue for the bug you're running in to? @MaherJendoubi we haven't look at the docker scenario as yet. I filed #31908 to investigate what it would take for us to support it. @sander1095 sorry for the late response, but we expect most .NET 6 workloads to work by the end of 6.0. The way it manifests might be different - for instances Blazor apps can re-render when a hot reload event happens, but a view or an API with swagger would require a browser refresh to see the update, but we expect changes to be applied to apps without needing a rebuild. |
Closing this as the initial set of features have landed in the preview3 and preview4 milestones and soon in VS. |
.NET 6.0 is introducing support for Hot Reload during development.
This issue is tracking ASP.NET Core specific changes required to make the developer experience great when code changes are applied via the new Hot Reload feature in .NET 6.0. These code changes are anticipated to be those supported by the runtime's Edit and Continue feature, or new versions of an entire type, in cases where ASP.NET Core could support appropriate remapping to the new type (e.g. a Razor View).
The text was updated successfully, but these errors were encountered: