Home/ Questions/Q 8424867
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-10T04:07:20+00:00

I have a small .NET component, exposing COM interface to legacy clients. The interface

  • 0

I have a small .NET component, exposing COM interface to legacy clients. The interface itself is very simple (4 methods) and parameters are all of simple types (strings, ints, etc.). The component internally uses a web service – added as service reference – which exposes large set of classes. When I generate COM type library from my component, all the types from the web service make it in – even though there is no need for it. What do I need to do to prevent that from happening? Can I somehow mark everything from the web service I’m consuming as private?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Exposing COM components is a pain, is your entire project comvisible? I would recommend not marking it comvisible then explicitly marking each class you want exposed with the comvisible (true) attribute. I believe the first link is your exact issue.

    A couple references you can look at:

    How to elegantly prevent a webservice proxy from being exposed to COM?

    Why is marking an assembly ComVisible(true) discouraged?

    • 0