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

[release/8.0-rc2] IDispatch should accept HRESULT as valuetype #92494

Merged
merged 4 commits into from
Sep 23, 2023

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Sep 22, 2023

Backport of #92447 to release/8.0

/cc @AaronRobinsonMSFT @elinor-fung @jkoritzinsky @JeremyKuhne @lonitra

Customer Impact

This is a regression from .NET Framework.
The current behavior has existed since IDispatch was introduced into .NET Core. This was discovered in WinForms during testing using CsWin32 generated COM interfaces.

Testing

Added tests for the current behavior.

Risk

Minimal. This is enabling a narrow feature that has been broken since .NET Core 3.0. This code path is also limited to IDispatch​ scenarios.

IMPORTANT: If this backport is for a servicing release, please verify that:

  • The PR target branch is release/X.0-staging, not release/X.0.

  • If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

@AaronRobinsonMSFT AaronRobinsonMSFT added this to the 8.0.0 milestone Sep 22, 2023
@AaronRobinsonMSFT AaronRobinsonMSFT added the Servicing-consider Issue for next servicing release review label Sep 22, 2023
Copy link
Member

@jeffschwMSFT jeffschwMSFT left a comment

Choose a reason for hiding this comment

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

approved. we will take for consideration in RC2

@carlossanlop
Copy link
Member

@AaronRobinsonMSFT this is targeting release/8.0, which represents RTM. If your intention is to target RC2, please retarget the branch by editing the PR title. Make sure no spurious commits get added unexpectedly when retargeting branch. Today EOD is the deadline for merging RC2 backports.

@AaronRobinsonMSFT AaronRobinsonMSFT changed the base branch from release/8.0 to release/8.0-rc2 September 22, 2023 20:40
@AaronRobinsonMSFT AaronRobinsonMSFT changed the title [release/8.0] IDispatch should accept HRESULT as valuetype [release/8.0-rc2] IDispatch should accept HRESULT as valuetype Sep 22, 2023
@AaronRobinsonMSFT AaronRobinsonMSFT changed the title [release/8.0-rc2] IDispatch should accept HRESULT as valuetype [release/8.0] IDispatch should accept HRESULT as valuetype Sep 22, 2023
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.
@carlossanlop carlossanlop changed the title [release/8.0] IDispatch should accept HRESULT as valuetype [release/8.0-rc2] IDispatch should accept HRESULT as valuetype Sep 22, 2023
@radical radical removed their request for review September 22, 2023 20:47
@AaronRobinsonMSFT AaronRobinsonMSFT added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Sep 22, 2023
@carlossanlop carlossanlop merged commit 1e50b05 into release/8.0-rc2 Sep 23, 2023
120 of 122 checks passed
@carlossanlop carlossanlop deleted the backport/pr-92447-to-release/8.0 branch September 23, 2023 02:05
@radical radical mentioned this pull request Sep 26, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Oct 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Interop-coreclr Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants