Subject: Forcing a .NET obj exposed as COM to use StdCall instead of CdCall

[Guest]

Does anyone know how to force interop to use a stdcall interface on the COM objects it creates instead of the cdcall interface that is standard

This is very importiant for my project. I need to reference a VB.NET based interop COM object from an outside program. The program will only interact with a stdcall interface on the COM object. .NET interop uses the cdcall interface when it exposes an assembly to COM. I need to figure out how to change this

Thanks for any help

-Dou

 

[Tian Min Huang]

Hello Doug,

Thanks for your post. I reviewed your description carefully, and now I'd
like to share the following information with you:
COM objects it creates instead of the cdcall interface that is standard?

Please kindly note that classic COM calling convention is based on IUnknown
and __stdcall, so thre is no need to change the calling convention.

p/s: I am not sure why you think Cdecl is standard.

Hope this helps.

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.