-
Notifications
You must be signed in to change notification settings - Fork 5k
Change to GetLastPInvokeError where possible #73980
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
Conversation
Tagging subscribers to this area: @dotnet/area-meta Issue DetailsWe added This now uses it whereever it's available. No functional change.
|
c27f665
to
673b957
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM if it builds, but I expect it's going to fail... some of these projects target pre-.NET 6, where GetLastPInvokeError was added.
Hmm, I did "build libs -allconfigurations".. is there more? We will see. |
Oh! Tests too. |
673b957
to
53312ad
Compare
@stephentoub looks like it's going to build - do you want to sign off? |
We added
Marshal.GetLastPInvokeError()
a while back, and madeGetLastWin32Error()
an alias for it, in order to reduce the use of "Win32" in non Windows contexts.This now uses it whereever it's available. No functional change.