-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Improve IDisposable inheritance examples #8117
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
Docs Build status updates of commit 67e6cca: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
Docs Build status updates of commit 67e6cca: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
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.
Thanks @MSDN-WhiteKnight This is great, and I'll now.
Update IDisposable inheritance examples to use FileStream instead of IntPtr.Zero safe handle. Using IntPtr.Zero handle is invalid and causes issues in Linux, where zero handle refers to stdin stream. There are some unrelated changes in VB, they are needed to make project compile, because there were name collisions.
Related to: dotnet/runtime#64305