-
Notifications
You must be signed in to change notification settings - Fork 353
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
Gen facades cleanup #7401
Gen facades cleanup #7401
Conversation
892fe2a
to
7919fe8
Compare
One thing I was thinking about as interesting to potentially improve perf would be moving this to a C# source generator. |
The not supported compile file is definitely a valid use case for a source generator. Would be interesting how much work it would be to switch from the task to the source generator and how much time we would save by that. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, make sure we thoroughly test the cleanup.
@@ -9,7 +9,6 @@ | |||
<!-- Libs --> | |||
<CommandLineParserVersion>2.2.1</CommandLineParserVersion> | |||
<CredentialManagementVersion>1.0.2</CredentialManagementVersion> | |||
<MicrosoftCciVersion>4.0.0-rc3-24214-00</MicrosoftCciVersion> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Surprised me to see this, I realized it was because Cci.Extensions didn't use the property:
<PackageReference Include="Microsoft.Cci" Version="4.0.0-rc3-24214-00" /> |
Tested locally against runtime main and found some issues which I fixed in the last commit. Merging. |
SourceFilesProjectOutputGroup
target so that the GenFacades package doesn't need to be referenced by contract projects anymore.IntermediateTargetPath
property in it_
internal ones.Before merging I want to wait for dotnet/runtime#52793 to be merged and then test the change in dotnet/runtime via a private package feed.