We're having an inconsistent problem with marshaling an ENUM value.
The ENUM is a third argument in a method, after two BSTRs.
When (and only when) the length of the second BSTR is odd, we sometimes
receive garbage as the enumerator value
 in the server.
Whenever this happens, the problem is solved by re-registering the
proxy-stub in the server (it is registered already, and
 we've checked that the registry doesn't actually change after the
re-registration).

Has anyone got an idea what's the story here ?

The ENUM is defined in a ".h" file imported into our IDL.
We're using the "oicf" option for building the proxy-stub.

Could this be prevented by using the V1_ENUM attribute ? (it looks like
some kind of an allignment problem)
Could it be related to using "oicf" ?

Any help would be greatly appreciated.

Thanks,

Ofer Sharon
 <<...OLE_Obj...>>
Tel: (972)-3-767-8656
Email: ofer_sharonpersay.com

----------------------------------------------------------------
Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html .
To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]