Comma Bug in Macros

KenWilson

I could not find an appropriate forum that dealt with just the Visual Studio environment itself, in particular macro processing. I am posting my problem here as it affects every C++ file I create.

The problem I have is with the macro processor's inability to deal with embedded commas in text strings. It appears any instance of a comma in a text string crashes the macro processor with the following error:

Unspecified error (Exception from HRESULT: 0x80004005(E_FAIL))

This has a very big negative impact on production as a large number of macros are no longer useable and I have to manually recreate the macro's intended output every time it is needed. Macros are used to create file headers and produce large blocks of code that are used often in the production cycle of any given project. Is there a fix for this comma bug

One annoying feature of this bug is it does not break at the first comma in the first string it finds necessarily but will appear to run happily past commas and then suddenly hit one and blow up.

Simple Samples

KenWilson wrote:

Is there a fix for this comma bug

Where is the bug described What is the status of the bug

If you don't know the answers to those questions then you are assuming there is a bug and are therefore not describing it well enough for anyone to help you.

KenWilson

Simple Samples wrote:

KenWilson wrote: Is there a fix for this comma bug Where is the bug described What is the status of the bug If you don't know the answers to those questions then you are assuming there is a bug and are therefore not describing it well enough for anyone to help you.

I am not assuming there is a bug. I had macros that worked prior to the SP1 update and that no longer work since, ergo there is a bug. I have been able to locate the following items which also refer to this problem:

http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=1199314&SiteID=1

https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx FeedbackID=225977&wa=wsignin1.0

Unfortunately Microsoft has closed this bug effective April 3, 2007 as fixed and it isn't. I am hoping someone may be able to point me to a reasonable work around that is trivial to implement and a large number of macros are involved.

Simple Samples

KenWilson wrote:

I had macros that worked prior to the SP1 update and that no longer work since, ergo there is a bug. I have been able to locate the following items which also refer to this problem: http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=1199314&SiteID=1 https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx FeedbackID=225977&wa=wsignin1.0

Thank you. That is critical information that is needed to understand the problem. I hope there is now adequate information for someone to help you, but you should create a new bug report.

einaros

"Fixed" usually means that it has been fixed in the code for Visual Studio 2008 and / or a future service pack for 2005. If you need it fixed ASAP, you need to contact support. They may be able to provide you with a hotfix.

DaveSmith

So.... was there a hotfix Follow up. I'm having the same problem, and I think Microsoft should seriously consider fixing this problem... or at least say that they won't.