Consider having IVTable follow visibility configuration
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.5k
- Forks
- 123
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 9
Description
IVTable is currently hardcoded to internal. This makes it impossible to utilize by other assemblies when one has configured CsWin32 for public visibility. The fallout of this is that it is impossible to leverage the auto-generation of ComWrappers CCWs in an external project (as done with the IManagedWrapper pattern that WinForms uses).
The requested fix is just to follow whatever the visibility configuration is.
Note that this comes up in my personal project, not WinForms, as WinForms does not publicly expose the generated CsWin32 interop.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the IVTable generation and the CsWin32 visibility configuration, then compare the generated declaration with the IManagedWrapper pattern linked in the issue. Done means IVTable uses the configured visibility so an external project can leverage generated ComWrappers CCWs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100