If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register or Login
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

[RESOLVED] Leave 'as is'

Hi,

I used VC 7 and 8 and also 6 a short time. I use VC because it is no option for me, to add mixed code, or a dotnet assembly with wrappers only to COM interfaces, while I must be sure, that my clients =will be= supporting DotNet 2.0 down to windows 2000.
So I use VC++ 8.0

My biggest advise: Don't *touch* VC syntax anymore!

I used to have big chunks of code in VC 7, and it used attributes. Some guys found those attributes not OK, so everything has been modified (ole db templates, COM attributes etc).
Where the attributes in VC 8 a success? Not at all. So I had to modify my code to non-attributed and this led to bugs again, in my code.

I would like to see that ATL would be updated to using newest APIS if the environment is compiled for XP and higher.

Re: Leave 'as is'

I used to have big chunks of code in VC 7, and it used attributes. Some guys found those attributes not OK, so everything has been modified (ole db templates, COM attributes etc).

From my perspective - Attributed ATL programming didn't turn out to be the success it was anticipated to be.

One indicator of this is that attributes on ATL projects were the default option in VC++ 7.x and made non-default for VC++ 8.0. I personally too find Attributed COM Programming a real tedium, and was happy to note that it was not default any more.

It will be great if somebody from Microsoft clarified on the company's stance on the future of Attributed ATL Programming - if there is any? Will any more effort be put into it?

Speaking for myself and many I know - we would not miss it in any way - in it's current state.