-
Notifications
You must be signed in to change notification settings - Fork 204
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
Invalid interop compatibility #168
Comments
What should be done here for HandleRef support? Usual stuff for Marshallers? Or any caveats? |
Yeah, I think HandleRef is the usual stuff. I think we already support it. Maybe not fully? This issue specifically tracks that if the HandleRef is invalid, we don't throw a descriptive exception. ( |
(I think the issue you're seeing with CreateStdAccessibleObject is caused by the object parameter. We don't have handling for other NativeType than AsAny - we need this to take the COM marshaller. Hopefully a single-line fix: |
Thanks for clarification. If one liner fix issues thats would be quite good. |
Related to dotnet#167 and Closes dotnet#168
Related to dotnet#167 and Closes dotnet#168
Related to dotnet#167 and Closes dotnet#168
Related to dotnet#167 and Closes dotnet#168
This is marshaller used when there incorrect configuration of marshaller applied to fields mostly Closes dotnet/runtimelab#168
Interop/PInvoke/Array/MarshalArrayAsField/AsLPArray/AsLPArrayTest
Interop/PInvoke/Miscellaneous/HandleRef/HandleRefTest
The text was updated successfully, but these errors were encountered: