Skip to content
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 we're compliant with latest Guidance #71

Open
thargy opened this issue Nov 21, 2018 · 1 comment
Open

Ensure we're compliant with latest Guidance #71

thargy opened this issue Nov 21, 2018 · 1 comment
Labels
cosmetic A cosmetic bug doesn't cause broken functionality question A question regarding existing features
Milestone

Comments

@thargy
Copy link
Contributor

thargy commented Nov 21, 2018

Microsoft have published updated .NET Standard Library Guidance. We should review our change to ensure compliance with best practices.

@thargy thargy added question A question regarding existing features cosmetic A cosmetic bug doesn't cause broken functionality labels Nov 21, 2018
@thargy thargy added this to the V6 Release milestone Nov 21, 2018
@thargy
Copy link
Contributor Author

thargy commented Nov 21, 2018

Note #67 is covered by the sourcelink guidance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cosmetic A cosmetic bug doesn't cause broken functionality question A question regarding existing features
Projects
None yet
Development

No branches or pull requests

1 participant