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

System.Drawing.Common library should conform to interop guidelines #51565

Closed
mthalman opened this issue Apr 20, 2021 · 1 comment · Fixed by #77565
Closed

System.Drawing.Common library should conform to interop guidelines #51565

mthalman opened this issue Apr 20, 2021 · 1 comment · Fixed by #77565

Comments

@mthalman
Copy link
Member

The following list of directories do not conform to the interop guidelines:

Specifically, the file organization section states that all Interop.*.cs files should all be defined in the Common directory. Conforming to the guidelines and having a standardized way of defining native interop supports the work for being able to track and detect platform dependencies.

@dotnet-issue-labeler dotnet-issue-labeler bot added area-Interop-coreclr untriaged New issue has not been triaged by the area owner labels Apr 20, 2021
@ghost
Copy link

ghost commented Apr 20, 2021

Tagging subscribers to this area: @safern, @tarekgh
See info in area-owners.md if you want to be subscribed.

Issue Details

The following list of directories do not conform to the interop guidelines:

Specifically, the file organization section states that all Interop.*.cs files should all be defined in the Common directory. Conforming to the guidelines and having a standardized way of defining native interop supports the work for being able to track and detect platform dependencies.

Author: mthalman
Assignees: -
Labels:

area-Interop-coreclr, area-System.Drawing, untriaged

Milestone: -

@safern safern removed the untriaged New issue has not been triaged by the area owner label Apr 20, 2021
@safern safern added this to the 6.0.0 milestone Apr 20, 2021
@safern safern modified the milestones: 6.0.0, 7.0.0 Jul 22, 2021
@ViktorHofer ViktorHofer modified the milestones: 7.0.0, Future Aug 4, 2022
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Oct 27, 2022
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Oct 31, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Nov 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants