-
Notifications
You must be signed in to change notification settings - Fork 391
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
Remove dependency upon Microsoft.VisualStudio.SDK.EmbedInteropTypes #9289
Conversation
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
in the EmbedInteropTypes package and ensure only the dependencies we need are embedded and the others are | ||
skipped. | ||
--> | ||
<Target Name="CustomLinkVSSDKEmbeddableAssemblies" AfterTargets="LinkVSSDKEmbeddableAssemblies"> |
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.
Are we sure this is no longer needed? While we may no longer need Microsoft.VisualStudio.SDK.EmbedInteropTypes, I would expect we still need to be careful about what we do or do not embed.
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.
It should be a simple matter to search for each of these target names in the codebase (or a binlog file) to see if anyone references them.
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.
I suppose the definitive answer would be to build with and without this change and see if there are changes in what gets embedded.
Though if the guidance for 64-bit VS is to not embed interop types and that is the default behavior then we're probably best off removing all of this non-default embedded behavior and just dealing with the fallout (if any).
Fixes #9286
Microsoft Reviewers: Open in CodeFlow