Skip to content

Conversation

@AaronRobinsonMSFT
Copy link
Member

This is a regression from .NET Framework.
The current behavior has existed since
IDispatch was introduced into .NET Core.
Added tests for the current behavior.

This is a regression from .NET Framework.
The current behavior has existed since
IDispatch was introduced into .NET Core.
Added tests for the current behavior.
@AaronRobinsonMSFT
Copy link
Member Author

/cc @dotnet/interop-contrib

Copy link
Member

@jkoritzinsky jkoritzinsky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@AaronRobinsonMSFT
Copy link
Member Author

@jkotas I don't see any obvious concern with this change, do you have any historical insight that I could be missing? The PropagateOutParametersBackToCallsite() is now only used in this late-bound case so I'm confident we are in a good place for this specific scenario.

@jkotas
Copy link
Member

jkotas commented Sep 22, 2023

@jkotas I don't see any obvious concern with this change, do you have any historical insight that I could be missing?

I do not have any obvious concerns either.

@AaronRobinsonMSFT AaronRobinsonMSFT merged commit 3fbf401 into dotnet:main Sep 22, 2023
@AaronRobinsonMSFT AaronRobinsonMSFT deleted the fixup_idispatch_hresult branch September 22, 2023 18:27
@AaronRobinsonMSFT
Copy link
Member Author

/backport to release/8.0

@github-actions
Copy link
Contributor

@ghost ghost locked as resolved and limited conversation to collaborators Oct 22, 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.

4 participants