Skip to content

Suggestion: Add an MSCOMM32.ocx wrapper. #2

Description

@johngardner58work

Note I am not saying that it needs to be an ACTIVE X / COM component though that would be fine. I personally would just call the native interfaces directly via .NET and avoid the marshalling. Still there might be people who would like the COM interfaces so they could call it from Excel. And possibly a provided PIA

  • Should support .NETStandard2.0 and be consumable by a .net9 application
  • Should expose all the same interfaces that the 6.0 version supports.
  • New improved interfaces are acceptable (overloads). Note COM can't use overloads so you might have to be explicit about what is exposed to COM and what isn't

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions