Microsoft KB Archive/158723

= How To Use BSTR, VARIANT, SAFEARRAY Types in Custom Interface =

Article ID: 158723

Article Last Modified on 3/3/2005

-

APPLIES TO

 Microsoft COM+ 2.0 Standard Edition, when used with:  Microsoft Windows NT 3.51 Service Pack 5

 Microsoft Windows NT 4.0

 Microsoft Windows 95 

-

<div class="notice_section">

This article was previously published under Q158723

<div class="summary_section">

SUMMARY
On platforms that do not support DCOM, such as Windows 95 without DCOM and versions of NT before NT 4.0, MIDL cannot generate marshaling code for custom interfaces that use the VARIANT, BSTR, or SAFEARRAY types. MIDL can generate marshaling code for such custom interfaces on platforms that support DCOM, such as Windows 95 with DCOM, NT 4.0 and later versions. This marshaling code can only be used on DCOM platforms; it cannot be used on platforms that do not support DCOM.

<div class="moreinformation_section">

MORE INFORMATION
Marshaling code for the VARIANT, BSTR, and SAFEARRAY types was available on platforms that do not support DCOM for use by the OLE Automation marshaler. However, this code was not exposed to other users, such as MIDL. Consequently, MIDL cannot generate marshaling code on these platforms for custom interfaces that use these types unless you provide your own marshaling code for these types. On platforms that support DCOM, the system providing marshaling code for these types is made available to MIDL.

If your custom interface uses BSTR, VARIANT, or SAFEARRAY, and if you want to use your custom interface marshaling code only on a DCOM platform, you can use MIDL generated marshaling code. You will need to use -D_WIN32_DCOM as a C compiler flag in the build process of the MIDL generated code. Otherwise, a compiler error will be generated that indicates that your code will compile only if you mark it as runable only on a DCOM platform.

If your custom interface uses BSTR, VARIANT, or SAFEARRA, and if you want to use your custom interface marshaling code on platforms that do not support DCOM, consider the following workarounds:.


 * Use LPSTR or LPWSTR instead of BSTR to pass strings. MIDL can generate code to marshal LPSTR and LPWSTR on all platforms. Use MIDL arrays instead of SAFEARRAY. Replace VARIANT with simple types or your own structure or union.
 * Use the OLE Automation marshaler to marshal your custom interface instead of using MIDL-generated marshaling code. The custom interface must be constrained to the OLE Automation-compatible types for this. The OLE Automation marshaler can marshal VARIANT and BSTR on all platforms.

<div class="references_section">