We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
On COM interfaces, we should express base interfaces using CLR base type metadata instead of NativeInheritanceAttribute.
As discussed on Teams, .NET can absolutely interop with COM interfaces that derive from each other. For example in VS we do it with this interface: https://docs.microsoft.com/en-us/dotnet/api/microsoft.visualstudio.shell.interop.ivsfilechangeex3?view=visualstudiosdk-2019
The text was updated successfully, but these errors were encountered:
Fixed in the latest version.
Sorry, something went wrong.
No branches or pull requests
On COM interfaces, we should express base interfaces using CLR base type metadata instead of NativeInheritanceAttribute.
As discussed on Teams, .NET can absolutely interop with COM interfaces that derive from each other. For example in VS we do it with this interface: https://docs.microsoft.com/en-us/dotnet/api/microsoft.visualstudio.shell.interop.ivsfilechangeex3?view=visualstudiosdk-2019
The text was updated successfully, but these errors were encountered: