You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In 0.3.49, we are now forced to do the dance that CsWin32 would previously do for us:
booladdedRef=false;try{// extract a HANDLE from the SafeFileHandle
_handle.DangerousAddRef(ref addedRef);if(PInvoke.ReadFile((HANDLE)_handle.DangerousGetHandle(), ptr,(uint)buffer.Length,&bytesRead, overlapped))return(int)bytesRead;}finally{
_handle.DangerousRelease();}
Context
CsWin32 version: 0.3.49-beta
Target Framework: net8.0
The text was updated successfully, but these errors were encountered:
Our project recently upgraded from 0.2.188 to 0.3.49. In doing so,
ReadFile
andWriteFile
were changed from taking aSafeHandle
to a rawHANDLE
.In 0.2.188, our invocation of
ReadFile
was:In 0.3.49, we are now forced to do the dance that CsWin32 would previously do for us:
Context
net8.0
The text was updated successfully, but these errors were encountered: