Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If I have the follwing assemblies:
MyComVisibleApi: a .Net assembly that is used by a VB app
MyReferencedAssembly: a .Net assembly referenced by MyComVisibleApi
Does MyReferencedAssembly need to be ComVisible if its functionality is never directly referenced by the VB App?
Thanks!
You shouldn’t have to make
MyReferencedAssemblyComVisibleunless you use types fromMyReferencedAssemblyin the public signatures ofMyComVisibleApi. Public signatures include properties, method parameters and return types.There is also a special case: if you derive a
ComVisibletype from a type that is notComVisible, public base class members will be exposed to COM as members of the derived class unless those members are individually[ComVisible(false)].