Re: wht's <projectnaname>PS.vcproj for?
And pay attention to MIDL warnings - treat them as errors.
A common cause of problems is ignoring the MIDL warning
that your interface is not Automation-compatible...
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================
"Kim Gr?sman" <kim@mvps.org> wrote in message
news:ba04ee015d6b68c8627eb7867e27@news.microsoft.com...
Hi,
Are the proxy/stub pairs absolutely necessary? Is there any case where
they are not needed at all, i.e. they can be deleted w/o worry?
A couple of cases where proxy/stub is not needed:
1) If your COM objects are not remotable (not even in the same process
between apartments) P/S is not necessary. 2) If your objects are apartment
neutral (aggregate the FTM) and are not used cross-process
3) If your interfaces are automation-compatible and described in a
typelibrary, you can let the OS handle marshalling based on the metadata
in the typelib.
The last one is accomplished by just mentioning your interfaces inside the
library block in the IDL, making sure they're automation compatible (mark
them with the [oleautomation] attribute, and MIDL will help you spot
incompatibilities). The typelibrary is embedded by default in your module,
and generally registered when your module is registered, so this should
just work.
--
Best regards,
Kim Gr?sman