How to post a generic bug report to Microsoft?

DotNetInterest

Hi All, I want to report a bug in the .NET framework. Any idea how to do this. I know ther eis this support.microsoft.com site. But it looks like it needs a MSDN / Product paid subscriber ID or a payment (via credit card),etc, even to post a generic bug report. Is there any other way to raise a generic bug rreport on MS product, specifically .NET framework 1.1, so MS can take a look at it?

Super Lloyd

Yes, I have an idea about it, glad you ask! :cool: To answer the second question: yes, there is way! :-D What else would you like to know? Ho... it just dawn on me that perhaps you want an URL where to conduct such action perhaps? Is it what you want? VC# Express => menu Community => Send feedback Here you go[^]! Although it requires a (free) .NET passport ...

DotNetInterest

Cheers, yes I wanted a website URL (I should have been specific about this, sorry!) to post bugs on .NET Framework 1.1. Also the link to VC# express site may not be helpful (i am not too sure though!) since i have this bug specifically on MS.NET Framework 1.1 :-( -- modified at 7:18 Tuesday 30th May, 2006

leppie

I would be interested to know about the bug, post some details (maybe in the .NET forum...) :)**

How xacc.ide transforms text to colored words on the screen
Intel PentuimM (aka Centrino) undervolting

**

realJSOP

Type it up in notepad, print it out, and then toss it in the trash. That's what they do at Microsoft, so you may as well just go ahead and do it yourself. Think of the time it will save everyone involved...

"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001

Super Lloyd

So would you better understand if I say? Click on this Link[^]! Incidentally this is the same link as above - MS feeback. But I did not mention "it that should not be named", in order to avoid to confuse you ... :doh: [Edit] I see, they say VS2005 all over the places, that doesn't prevent you to post a .NET 1.1 feedback. That's the best place to do so anyway! And there is a ".NET Framework" category. I did write feedback here 4 times and I had prompt and useful feedback.. (in a matter of days..)

Rob Graham

Actually, I suspect their marketing department looks them over to see if the bug has potential as a new feature...

Anish M

I too would like to know what the bug is, if its not a secret

Jim Crafton

Actually the tool of choice is now PowerPoint, so that you can use gradients to emphasize action points. It still goes in the garbage, but at least now you can print it up in color. ¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! -- modified at 9:51 Tuesday 30th May, 2006

Mark II

IMHO, I think it is often better to publish the bug in a discussion forum first. If the community agrees that a bug exists, this can have a number of benefits (1) gives you confidence (2) stengthens your case that there is a bug (3) encourage others to report the same bug (4) can help you understand the bug better if others are investigating it as well (5) may help provide work-arounds (6) warns everyone else that the bug exists so that they don't have to duplicate your work. OTOH, there is always the possiblilty that what appears to be a bug may, in fact, be something else. This has happended to me twice very recently. The first time was to report a bug in the 2.0 framework. I learned from the community that the crazy behaviour I observed was not actually a bug, but was actually the intended behaviour of the class I was using. The second occasion was to report a problem with the 2.0 Enterprise Library. This time I learned that the problem was not a bug with the library, but a (poorly documented) change between versions 1.0 and 2.0.