Attributed C++ programming with Smart Devices (VS2005)?

[Smith]

Are attributed ATL projects be supported under Whidbey for Smart Devices?

The New ATL Project dialog box doesn't have the 'Attributed' check box for
smart devices projects in Beta1, but Win32 desktop projects do have this
checkbox.

When I add a new class to my ATL Smart Device project and select for
instance an ATL Simple Object, I do have the possibility to generate an
attributed class. However, when I build I get the following errors:

fatal error CVT1100: duplicate resource . type: TYPELIB, name:1,
language=0x0409
fatal error LNK1123: failure during conversion to COFF: file invalid or
corrupt.

I need to know whether attributed COM programming is supported or not for
Smart Devices in Visual Studio .NET 2005. If this is not the case I won't
spend time trying to fix Beta1 bugs.

[William DePalo [MVP VC++]]

"Smith" <Sm***@smith.com.invalid> wrote in message
news:%2***************@TK2MSFTNGP14.phx.gbl...

I need to know whether attributed COM programming is supported or not for
Smart Devices in Visual Studio .NET 2005. If this is not the case I won't
spend time trying to fix Beta1 bugs.

I don't know.

It's not what you asked, but I can tell you when I recently asked an ATL
expert whom I know if I should upgrade an old un-attributed ATL project I
built with VS6 to an attributed one with VS.Net 2003 he replied

<quote>
Most people that frequent microsoft.public.vc.atl agree that attributed
code is best to be avoided. The atrribute-generated code has certain
major bugs, and the worst part is that you cannot easily look at the
code nor fix it. I recommend leaving attributed ATL programming very
much alone.
</quote>

So, I can't tell you what the official stance is from on high, but the view
from the trenches is not pleasant. You might want to post again the ATL
group.

Regards,
Will