-
Notifications
You must be signed in to change notification settings - Fork 301
.NET to COM Conversion Documentation
The following links provide technical documentation on how COM interop will expose .NET types to COM clients, and include information on what attributes will be controlled and which will not be covered. The documentation also describes the naming or decorating behaviors to ensure that the result of conversion compiles with COM requirements. For example, overloading is not allowed in COM, so the documentation describes behavior in those case.
Note: Because Rubberduck uses custom build process, which includes a MIDL compilation step, we are not constrainted by the behavior described. However, we do need to override the unwanted behavior (e.g. In the case of enum naming), so understanding the current behavior is essential for handling the customization correctly.
rubberduckvba.com
© 2014-2021 Rubberduck project contributors
- Contributing
- Build process
- Version bump
- Architecture Overview
- IoC Container
- Parser State
- The Parsing Process
- How to view parse tree
- UI Design Guidelines
- Strategies for managing COM object lifetime and release
- COM Registration
- Internal Codebase Analysis
- Projects & Workflow
- Adding other Host Applications
- Inspections XML-Doc
-
VBE Events