-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Ensure Microsoft.Interop.SourceGeneration ships #74943
Ensure Microsoft.Interop.SourceGeneration ships #74943
Conversation
Also fix the LibraryImportGenerator and JSImportGenerator to package Microsoft.Interop.SourceGeneration correctly (should IsPackable ever be set).
Tagging subscribers to this area: @dotnet/interop-contrib Issue DetailsAlso fix the LibraryImportGenerator and JSImportGenerator to package Microsoft.Interop.SourceGeneration correctly (should IsPackable ever be set).
|
...ies/System.Runtime.InteropServices.JavaScript/gen/JSImportGenerator/JSImportGenerator.csproj
Outdated
Show resolved
Hide resolved
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
These are referenced by eng\generators.targets not just the package.
@AaronRobinsonMSFT - as part of attempting to remove the packaging, I noticed that the package redistributed https://github.com/dotnet/runtime/blob/main/src/libraries/System.Runtime.InteropServices/gen/LibraryImportGenerator/Microsoft.Interop.LibraryImportGenerator.props. I see we import this in runtime targets. What's the story for end-customers consuming the inbox generator? I didn't see those items added by the SDK targets anywhere: https://github.com/search?q=org%3Adotnet+LibraryImportGenerator_UseMarshalType&type=code |
@ericstj At present, this is only for our own internal testing and develop needs. No user should ever need these settings. It is possible we will add some in the future but we can handle that when it becomes a user configuration. |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-perf |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Feel free to merge before the wasm tests finish
Thanks @lewing. I'll be online today - if anyone is seeing more fallout from this or the previous change, please ping me on teams and I'll take a look right away. |
Fixes: #74944
Also fix the LibraryImportGenerator and JSImportGenerator to package Microsoft.Interop.SourceGeneration correctly (should IsPackable ever be set).