Re: How to generate errors from attribute COM project, VS .NET 2003
MS is listening, yes - they have disabled the attributed checkbox
for new ATL projects by default in VC 8 (VS 2005).
My personal opinion, which I suspect is shared by most of the
experts in this group is that Microsoft should never have attempted
the attributed ATL COM in the first place. Attributed ATL is
great for attributed ATL OLE DB, as well as ATL Server, but
they should have stopped there...
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================
"mellery451" <mellery451@gmail.com> wrote in message
news:1188497024.359821.299690@r23g2000prd.googlegroups.com...
On Aug 29, 11:03 pm, "SvenC" <Sv...@community.nospam> wrote:
Hi,
mellery...@gmail.com wrote:
using VS.NET 2003, I created a COM server that uses attributed code.
Don't do it. Attributed COM has some issues/bugs which make your life
harder. Check this newsgroups to verify that.
noted -- I've seen a number of posts here that seem to confirm your
statement. Too bad -- attributed code certainly seems to simplify
some things for the coder. I hope MS is listening and can resolve
some of the issues with attribute engine, etc.
You could use the function AtlReportError.
OK - I'll try that -- but the CComCoClass::Error is just a thin
wrapper around AtlReportError, so it amounts to the same thing.
Start your error codes from 0x80040200 up to 0x8004ffff. I am not sure
but
maybe you get standard error messages for a standard error codes. That
might
be a limitation of how the COM client (the script engine in your case)
handles error codes.
aha - this seems to do the trick. In ATL projects, I used to get away
with using some of the basic error codes (E_FAIL, E_INVALIDARG, etc)
in my calls to Error() and I would still get my custom message, but I
guess something is different enough in the generated base classes that
this no longer applies. Thanks for your help.
-Mike