-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Document API platform differences #21115
Comments
Update also porting.md - AppDomains with link to differences. |
@karelz do you think this can be done in v2.0 time frame? I think this will need sometime to cover such differences |
This should happen in 2.0 timeframe - it is part of the platform end-to-end. It might be exemption to ZBB on 5/10 though. |
BTW: The content/list of differences is now being collected here: https://github.com/dotnet/corefx/wiki/ApiCompat |
@karelz Post-ZBB label maybe? |
Yep, good catch. Thanks @ViktorHofer! |
@karelz are you following in this? will be able to close it before the end of the week? |
I will follow up. Documentation changes can happen after Escrow ;) as they don't require code change. |
The tooling was released as preview via nuget: https://blogs.msdn.microsoft.com/dotnet/2017/10/31/introducing-api-analyzer/ Source code is here: https://github.com/dotnet/platform-compat |
We need to document API differences:
The documentation should be exposed as platform-compat tooling and also as standalone HTML.
The text was updated successfully, but these errors were encountered: