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.

Sign up for GitHub

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

Jump to bottom

Support Dev inner loop improvements in CoreCLR VM #45629

Closed
tommcdon opened this issue Dec 5, 2020 · 4 comments
Closed

Support Dev inner loop improvements in CoreCLR VM #45629

tommcdon opened this issue Dec 5, 2020 · 4 comments
Labels
area-Diagnostics-coreclr User Story A single user-facing feature. Can be grouped under an epic.
Milestone
6.0.0

Comments

@tommcdon
Copy link
Member

tommcdon commented Dec 5, 2020 •
edited by marek-safar
Loading

Contributes to dotnet/core/issues/5511

Overview

Our goal is to provide a consistent dev inner loop experience in .NET Core across all platforms, architectures, and workloads. Today, code edits can be made at runtime and applied to running processes using ReJIT and Edit and Continue . The typical dev inner loop involves making code edit changes, building, debugging, then making new edits. Edit and Continue can apply code edits while the debugger is attached and given that it conforms to a set of constraints (defined here). Our desire is to improve the inner loop and by allowing code edits to applied at runtime and support multiple platforms/architectures. Ideally this work will involve using the same/similar API's being used for Mono Method Body Replacement.
@tommcdon tommcdon added this to the 6.0.0 milestone Dec 5, 2020
@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added the untriaged New issue has not been triaged by the area owner label Dec 5, 2020
@ghost
Copy link

ghost commented Dec 5, 2020

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

Issue Details

Contributes to dotnet/core/issues/5511

Overview

Our goal is to provide a consistent Hot Reload experience in .NET Core across all platforms, architectures, and workloads as described in dotnet/core/issues/5511. Today, code edits can be made at runtime and applied to running processes using ReJIT and Edit and Continue . The typical dev inner loop involves making code edit changes, building, debugging, then making new edits. Edit and Continue can apply code edits while the debugger is attached and given that it conforms to a set of constraints (defined here). Our desire is to improve the inner loop and by allowing code edits to applied at runtime and support multiple platforms/architectures. Ideally this work will involve using the same/similar API's being used for Mono Method Body Replacement.

Author: tommcdon
Assignees: -
Labels:

area-Diagnostics-coreclr
Milestone: 6.0.0

@tommcdon tommcdon removed the untriaged New issue has not been triaged by the area owner label Dec 5, 2020
@srxqds
Copy link
Contributor

srxqds commented Dec 5, 2020

will mono support it in jit mode?

@tommcdon
Copy link
Member Author

tommcdon commented Dec 5, 2020

will mono support it in jit mode?

Please see #44806 for the mono hot reload work

@tommcdon tommcdon changed the title Support Hot Reload in .NET Core Support Dev inner loop imrpvements in .NET Core Dec 5, 2020
This was referenced Dec 5, 2020
Closed
Closed
@tommcdon tommcdon changed the title Support Dev inner loop imrpvements in .NET Core Support Dev inner loop improvements in .NET Core Dec 7, 2020
@tommcdon tommcdon added the User Story A single user-facing feature. Can be grouped under an epic. label Dec 9, 2020
@lambdageek lambdageek mentioned this issue Jan 21, 2021
Closed
@marek-safar marek-safar mentioned this issue Feb 4, 2021
Closed
2 tasks
@marek-safar marek-safar changed the title Support Dev inner loop improvements in .NET Core Support Dev inner loop improvements in CoreCLR VM Feb 4, 2021
@lambdageek lambdageek mentioned this issue Mar 23, 2021
Closed
@tommcdon
Copy link
Member Author

Hot Reload is now enabled on .NET Core and Mono, closing

@ghost ghost locked as resolved and limited conversation to collaborators Jul 21, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area-Diagnostics-coreclr User Story A single user-facing feature. Can be grouped under an epic.
Projects
None yet
Milestone
6.0.0
Development

No branches or pull requests
4 participants
@srxqds @tommcdon @Dotnet-GitSync-Bot and others