I have recently reported a private bug to Microsoft, a "C++ CodeDOM parser error: Internal Error", which blocks my efforts to continue component development for one of my components in C++/CLI. The bug was reported a week ago but has evidently not been reviewed by Microsoft. The bug is detailed at http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=671820&SiteID=1 on this site.
Is there a way to contact Microsoft directly so that I can have this bug looked at and so that I can get a workaround or fix which enables me to successfully complete and market my component
Also, does anyone know whether file attachments added to public bug reports are downloadable by all users or only by Microsoft I made my bug report private because I did not want othhers downloading the component which illustrates the bug, but if the file attachments are not downloadable by the general public I will make the bug report public instead.
Getting bug report support from Microsoft
Hot Topic
- Annoying change from VS 2003 to 2005: Can it be rectified?
- fatal error RC1107: invalid usage; use RC /? for Help
- set<String> in Visual C++ .NET
- How to read file as BYTE array into program?
- Use of __m128i as two 64 bits integers
- "cannot use this type here without a top-level '^'"
- Problem moving byte array from C# to Managed C++ and back
- error C2440: '<function-style-cast>' : cannot convert from 'UINT' to 'CString'
- Bitmap in win32 Console Application
- Problem with legacy application - ATL
Visual C++
- trouble with __declspec(dllimport)
- RUNTIME ERROR
- Embed and initialize unmanaged object in the managed wrapper class
- ReadProcessMemory crashes computer
- CWinFormsControl and VC.NEt
- Templates overloades and specializations
- Memory corruption possible with _SECURE_SCL ?
- deque iterator not dereferencable error
- C1189 Please use the /MD switch for _AFXDLL builds
- dll search order
Getting bug report support from Microsoft
Jordan Terrell
Have you tried calling Microsoft Support to open a support incident http://support.microsoft.com/contactus/
Robin E Davies
You can always ask me to followup
I tried looking at the Connect bug page but as it is private I can't see it. Luckily our internal bug tracking tool, which interfaces with Connect, has a reference to the page number (192618 in this case) so I was able to find the bug. The bug was still waiting for its initial processing - there seems to be some "issue" with this process as we tend to see the bug in spurts about once every two weeks - we've started to call them "Bug Bombs" - as suddenly 30 new bugs appear.
I have moved this bug over to the appropriate team and I'll make sure that they take a look today. So you can hold on to your $245 for now.
j1m68
Great ! I will take a look at it next week and hopefully there will be some workaround which will enable me to continue development of my component. Needless to say, if there is a real bug involved in the CodeDom C++ parser, I hope unearthing this bug will enable Microsoft to fix the CodeDom C++ parser in a future service pack.
David Ing
No one has responded to the bug report in the past week. I would have thought not only would they want to get me beyond my blocking issue but also that they would have wanted to solve at least one source of the CodeDom Parser error, since others had reported it before I did but none had supplied a project showing this bug in action, as I have done.
LLeuthard
Thank you but I do not know you or how to reach you personally.
I will be glad to change this to public as long as I am assured that the attachment is only accessible by Microsoft. If the attachment is accessible by any viewer of the bug I would like it to remain as a private bug report.
Thanks, that would be helpful. I do believe that if the bug is Microsoft's, which I am sure it is simply by the fact that whatever I might be doing wrong should produce an intelligent design time error message rather than an internal CodeDom Parser error, that I would not be charged the $245 but I am no longer sure of the policy.
billqu
The bug is now assigned to the right person, but they have a bunch of issues in front of that, so getting them to look at it "today" isn't going to happen. The developer should be able to take a look within a couple days though.
Thanks,
Curt Carpenter
Visual C++
Intikhab
My product is Visual Studio 2005 Standard Edition. It is not even listed among the Visual Studio 2005 products which have support at http://support.microsoft.com/oas/default.aspx &c1=501&gprid=3041& . I do not want to pay Microsoft $245 to fix their own bug, but I will try the number for the Professional Edition instead and, if I can not get help there I will call the number for the Express Edition.
faraaz_malak_c92eb4
1) moc.tfosorcim@sevacnoj
2) I would keep it as private - the attachment should be (and in your case it was) automatically propagated over to our internal bug tracking tool.
3) We don't charge for fixing bugs that are reported through the forums.