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

Add basic support for StringMarshalling in GeneratedComInterface #86404

Merged
merged 6 commits into from
May 18, 2023

Conversation

jtschuster
Copy link
Member

First step of #84662

Adds support for using StringMarshalling with GeneratedComInterfaceAttribute. There is no validation that all inheriting interfaces have the same StringMarshalling yet.

@dotnet-issue-labeler
Copy link

Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

@jtschuster jtschuster requested a review from jkoritzinsky May 17, 2023 19:09
@ghost
Copy link

ghost commented May 17, 2023

Tagging subscribers to this area: @dotnet/interop-contrib
See info in area-owners.md if you want to be subscribed.

Issue Details

First step of #84662

Adds support for using StringMarshalling with GeneratedComInterfaceAttribute. There is no validation that all inheriting interfaces have the same StringMarshalling yet.

Author: jtschuster
Assignees: jtschuster
Labels:

area-System.Runtime.InteropServices, new-api-needs-documentation

Milestone: -

@jtschuster jtschuster merged commit 3d7241a into dotnet:main May 18, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Jun 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants