BEGIN_MSG_MAP_EX breaks Visual Studio 2005 intellisense?

Question

I have a C++ application using WTL/ATL BEGIN_MSG_MAP_EX macros for message handling. I use some macros from atlcrack.h.

When we upgraded the projects to Visual Studio 2005, intellisense acts crazy. I've tracked the behavior down to the BEGIN_MSG_MAP_EX macro not behaving correctly with intellisense. However, I can not find a way to continue using BEGIN_MSG_MAP_EX and Visual Studio 2005.

Do I have to rewrite all my old message handlers and stop using BEGIN_MSG_MAP_EX or is there another fix?

Answer 1

I've been using WTL for years and haven't come across this issue, but I also find the default Intellisense in VS2005/2008 next to useless - it stops working for no apparent reason. If you want Intellisense to work the way God intended, I recommend you try Visual Assist X (free 30 day trial) - it might make your problem disappear - got to be better than changing your code to work around IDE problems?

http://www.wholetomato.com/