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

Expose EnC analysis APIs to Razor via External Access #50773

Closed
tmat opened this issue Jan 26, 2021 · 1 comment
Closed

Expose EnC analysis APIs to Razor via External Access #50773

tmat opened this issue Jan 26, 2021 · 1 comment

Comments

@tmat
Copy link
Member

tmat commented Jan 26, 2021

Required:

  • API for constructing SemanticEdit instances when sources are modified
    • Given CodeAnalysis.Document instances, returns Task<SemanticEdit[]> or similar
    • Also returns rude edit diagnostics

Possibly useful:

  • Given the above, some kind of common hot reload orchestrator that could run inside VS and “dotnet watch”, to convert the sequence of project source changes into a sequence of EmitDifferenceResult/metaStream/ilStream/pdbStream (or compilation errors) that can be transported to the runtime. This would take care of all the tracking of compilation state, updating baselines, error handling, etc.
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Interactive untriaged Issues and PRs which have not yet been triaged by a lead labels Jan 26, 2021
@tmat tmat added this to the 16.10 milestone Jan 26, 2021
@tmat
Copy link
Member Author

tmat commented Jan 26, 2021

@SteveSandersonMS

@jinujoseph jinujoseph added Concept-Continuous Improvement and removed untriaged Issues and PRs which have not yet been triaged by a lead labels Jan 26, 2021
@tmat tmat closed this as completed Jun 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants