-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
CodeBehindGenerator
has improper pipeline
#12978
Comments
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process. |
Note: I think this needs a second look from Roslyn team. |
@jonathanpeppers thoughts ? |
I asked in Teams (private link), where some of the Roslyn folks are. |
@Youssef1313 @jonathanpeppers @StephaneDelcroix any updates on this? |
The points in teams are:
You can define any type in XAML and then give it a One comment from the Roslyn team:
|
Verified this issue with Visual Studio Enterprise 17.9.0 Preview 1.0. Can repro on android platform. |
…hability - Split out CSS SourceGen, which does not depend on Compilation at all - Added TrackingNames to support new SourceGen unit test project Fixes Issue #12978 CodeBehindGenerator has improper pipeline Fixes AB#1947659: `CodeBehindGenerator` has improper pipeline
* - Restructured CodeBehindGenerator pipeline to maximize SourceGen cachability - Split out CSS SourceGen, which does not depend on Compilation at all - Added TrackingNames to support new SourceGen unit test project Fixes Issue #12978 CodeBehindGenerator has improper pipeline Fixes AB#1947659: `CodeBehindGenerator` has improper pipeline * - Use file-scoped namespaces throughout PR - Use raw string literals for SourceGen tests
* - Restructured CodeBehindGenerator pipeline to maximize SourceGen cachability - Split out CSS SourceGen, which does not depend on Compilation at all - Added TrackingNames to support new SourceGen unit test project Fixes Issue #12978 CodeBehindGenerator has improper pipeline Fixes AB#1947659: `CodeBehindGenerator` has improper pipeline * - Use file-scoped namespaces throughout PR - Use raw string literals for SourceGen tests
Completed with PR #20524. Not sure why it didn't auto-complete this item. |
Because the PR had |
maui/src/Controls/src/SourceGen/CodeBehindGenerator.cs
Lines 64 to 67 in 83c3ac9
This won't work well. Combining
CompilationProvider
and havingCompilation
as part of the pipeline will cause the generator to re-run on every change. So, it's not incremental at all. Note thatsourceProvider
is the last step.This also roots(Edit: I don't think there is a memory leak concern in this case)Compilation
objects in memory. See dotnet/roslyn-analyzers#6352The text was updated successfully, but these errors were encountered: