Do MS pay any attention to bug reports?
-
They seem to leave them for 6 months or so then mark them as resolved without doing anything, and then as closed after a year with the standard... 'Unfortunately another part is the reality of schedules and the need to get the bits into production. We have evaluated your suggestion and it does not meet the criteria to be addressed in this release'.
Dave
BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)
Visual Basic is not used by normal people so we're not covering it here. (Uncyclopedia) -
This was VS2008 and WPF. But, you raise a good point :P
Christian Graus Driven to the arms of OSX by Vista.
:laugh:
"mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"
-
Microsoft pays no-one! ;P
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 beta 2 - out now!
((lambda (x) `((lambda (x) ,x) ',x)) '`((lambda (x) ,x) ',x))they pay chuc..... oh wait wrong thread :rolleyes:
"mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"
-
They seem to leave them for 6 months or so then mark them as resolved without doing anything, and then as closed after a year with the standard... 'Unfortunately another part is the reality of schedules and the need to get the bits into production. We have evaluated your suggestion and it does not meet the criteria to be addressed in this release'.
Dave
BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)
Visual Basic is not used by normal people so we're not covering it here. (Uncyclopedia)Its called their WeSyp program. http://www.youtube.com/watch?v=Pc4j3pEoMXY
-
They seem to leave them for 6 months or so then mark them as resolved without doing anything, and then as closed after a year with the standard... 'Unfortunately another part is the reality of schedules and the need to get the bits into production. We have evaluated your suggestion and it does not meet the criteria to be addressed in this release'.
Dave
BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)
Visual Basic is not used by normal people so we're not covering it here. (Uncyclopedia)It sometimes does :) One of my major complaints about C++ source code regions is supposedly fixed in VS2010 :)
-
Microsoft pays no-one! ;P
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 beta 2 - out now!
((lambda (x) `((lambda (x) ,x) ',x)) '`((lambda (x) ,x) ',x))I did get my live.com cashback for just over $300 just last week. :) That brought my core2 quad q9550 system (6GB of quality DDR2 + Q9550 + ASUS P5Q Pro + ANTEC 650W 80+ PS) to around $420US. Also brought the price down on some other presents..
John
modified on Monday, February 9, 2009 7:30 PM
-
It sometimes does :) One of my major complaints about C++ source code regions is supposedly fixed in VS2010 :)
peterchen wrote:
complaints about C++ source code regions is supposedly fixed in VS2010
That is a big frustration of mine. I mean the fix is in a new version..
John
-
They seem to leave them for 6 months or so then mark them as resolved without doing anything, and then as closed after a year with the standard... 'Unfortunately another part is the reality of schedules and the need to get the bits into production. We have evaluated your suggestion and it does not meet the criteria to be addressed in this release'.
Dave
BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)
Visual Basic is not used by normal people so we're not covering it here. (Uncyclopedia)No. Why should they? If they sit on them for a few months they can discontinue the product and force us a buy a new set of bugs to remain "current."
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
-
They seem to leave them for 6 months or so then mark them as resolved without doing anything, and then as closed after a year with the standard... 'Unfortunately another part is the reality of schedules and the need to get the bits into production. We have evaluated your suggestion and it does not meet the criteria to be addressed in this release'.
Dave
BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)
Visual Basic is not used by normal people so we're not covering it here. (Uncyclopedia)In my experience bugs reported through "connect" are rarely worked on. If you are able to report them through the telephone technical support service that is available to partners the success rate is much greater. Although telephone tech support is a paid for service any report confirmed as a bug will be handled free of charge. The response will be proportional to the "criticality" of the problem so I would only recommend reporting serious problems that have no workaround through this route.
www.it-workplace.com
"If a man speaks in a forest where no woman can hear him is he still wrong?" -
They actually run an office pool betting on where the bugs are going to show up, how long the bug can be called "a feature" or "as design" before a user actually proves it exists, and how many times the same bug is reported. So, no, the bug reports aren't ignored.
"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/2001Now this I can believe!
Dave
BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)
Visual Basic is not used by normal people so we're not covering it here. (Uncyclopedia) -
In my experience bugs reported through "connect" are rarely worked on. If you are able to report them through the telephone technical support service that is available to partners the success rate is much greater. Although telephone tech support is a paid for service any report confirmed as a bug will be handled free of charge. The response will be proportional to the "criticality" of the problem so I would only recommend reporting serious problems that have no workaround through this route.
www.it-workplace.com
"If a man speaks in a forest where no woman can hear him is he still wrong?"Andrew Wiles wrote:
through "connect" are rarely worked on
Interesting.
Andrew Wiles wrote:
have no workaround
Yeah, I've been dubious about providing workarounds that I've found in case they think that they no longer need to bother. I think in future I'll keep that part to myself, or put in my CP blog that I've never used.
Dave
BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)
Visual Basic is not used by normal people so we're not covering it here. (Uncyclopedia) -
They seem to leave them for 6 months or so then mark them as resolved without doing anything, and then as closed after a year with the standard... 'Unfortunately another part is the reality of schedules and the need to get the bits into production. We have evaluated your suggestion and it does not meet the criteria to be addressed in this release'.
Dave
BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)
Visual Basic is not used by normal people so we're not covering it here. (Uncyclopedia)During the beta of VS 2005 I had a number of bugs fixed and closed (and I was really impressed with the service), but since then they have been mostly closing them saying, as you said, they don't have time. However, a few of my bugs have still been marked as fixed, or suggestions taken on board for future versions. Uusually, if all I get is the stock response (as you mention above) I post a comment complaining about a lack of individual feedback, and mark the bug re-opened. Someone usually looks at it again, and then posts a reply comment stating it's a good idea/bad idea, or it's by design/not by design or explaining why it's hard to fix. Sometimes they say they'll defintely look at it for the next release. At least that makes me feel a little better. Also, I contacted the connect team once to ask if anyone reviewed or was notified of comments posted to 'closed' tasks, and apparently it's best to re-open them if you're posting a comment you want a response to, otherwise it's likely to go ignored. In general, I think the best time to get a bug fixed is during a beta, and you're far more likely to get it fixed if it's a 'new bug' rather than one that has been around for several prior versions. Also, I wouldn't expect any suggestion to make it into the release they are currently working on, i.e if you made one within the last 12 months you shouldn't expect to see it before whatever comes after VS 2010, if it ever gets done at all.
-
In my experience bugs reported through "connect" are rarely worked on. If you are able to report them through the telephone technical support service that is available to partners the success rate is much greater. Although telephone tech support is a paid for service any report confirmed as a bug will be handled free of charge. The response will be proportional to the "criticality" of the problem so I would only recommend reporting serious problems that have no workaround through this route.
www.it-workplace.com
"If a man speaks in a forest where no woman can hear him is he still wrong?"I have had 3 of my Connect reports accepted ad bugs and fixed. Dave.
-
They seem to leave them for 6 months or so then mark them as resolved without doing anything, and then as closed after a year with the standard... 'Unfortunately another part is the reality of schedules and the need to get the bits into production. We have evaluated your suggestion and it does not meet the criteria to be addressed in this release'.
Dave
BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)
Visual Basic is not used by normal people so we're not covering it here. (Uncyclopedia)Of course MS cares! Have a look at this video: WSYP Project[^] :laugh:
Regards, Ricardo Corona
-
And I thought that the bugs are features!
;-]
Yes, Microsoft's bugs are features to the competition. Look at the Apple commercials. :laugh:
