-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Enable APICompat in WPF Builds #880
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
Conversation
…mblies are being built.
… exist. Starting implementation of repo-specific ApiCompat so that things just work when code is internal or public.
…sembly names are shared between lib/ref/cycle-breakers.
…never shipped as ref assemblies in .NET 4.8, so we don't need to verify compat for them.
…lished in .NET Framework.
… in the port. Some errors may still arise from the build here as there are open issues still.
Having some issues getting ref compat to run, working them out now. |
…m our compiler generated ref assemblies to .NET 4.8. This also will enable hand-crafted ref assembly compat vs the associate lib assembly and cycle-break api compat.
We can now run API compat both against .NET 4.8 and lib vs hand-crafted ref. Still don't have cycle-breakers working, but that's not much different from hand-crafted ref. |
src/Microsoft.DotNet.Wpf/ApiCompat/Baselines/PresentationBuildTasks-Net48.baseline.txt
Show resolved
Hide resolved
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.
See comments about documentation and improving the error message when api compat fails
I resolved your comments against the documentation. Let me know if you have any specific comments relating to that. |
Fixes #724
See: https://github.com/rladuca/ApiCompatNotes/blob/master/ApiCompat%20Notes.txt
This sets up and enables API Compat against .NET 4.8 reference assemblies and also ensures compat between hand-crafted ref assemblies and their lib counterparts.