I can only simpathize with you. At least you've learned
you adopt it. Attributed ATL is very high risk with little
benefit in my analysis. This not even considering the bugs
On Tue, 7 Nov 2006 16:17:58 -0800, "Brian Muth" <bmuth@mvps.org>
wrote:
Jenny, I have to warn you that you may not get a response here, simply
because pretty much all the experts here avoid attributed ATL. Attributed
ATL was very buggy under VS2003, and even under VS2005 the default is now
set to "unattributed", an indication that attributed ATL is being
de-emphasized.
I recommend that if you are going to make the effort to upgrade to VS2005,
now is a good time to change it to unattributed code. You will be better
off
in the long run, IMHO.
Brian
"Jenny" <jean.shu@gmail.com> wrote in message
news:1162939583.224985.21760@m73g2000cwd.googlegroups.com...
Hi,
I have a project that using attributed ATL to create a COM component.
This project compiles and runs well. It was originally developed using
vs2003. When I'm trying to convert the project to vs2005, it give me a
midl2025 error. It complains the interface forward declaration. How to
solve this? Here is the code. Thanks in advance.
[ export]
snipped
Brian, this seems like one heck of a debacle. Does Microsoft have any
tools to help "unattribute" code? Was this simply an oversight on
Microsoft's part? Usually when code is deprecated it at least
compiles, in this case many developers are stuck with large amounts of
code that will not build on Visual Studio 2005 without major
refactoring.
At the very least Microsoft should have documentation somewhere to
help the many people that are running into the problem.