BT
x Your opinion matters! Please fill in the InfoQ Survey about your reading habits!

VS 2010 Bugs Being Ignored?

by Jonathan Allen on Aug 04, 2009 |

It appears that Microsoft is no longer fixing minor bugs for VS 2010. Carlos Quintero has cited three bugs in EnvDTE that DJ has marked as “Won’t Fix” for this release. EnvDTE is the primary means by which .NET developers can build add-ons for Visual Studio.

The messages posted by DJ Park, the C# IDE Program Manager, follow this pattern:

Thanks for the feedback! Again, this is an issue that we would like to address but given that our current focus is on stabilizing and improving the performance of VS2010, we won't be able to address this issue for this release. I'm going to go ahead and resolve this bug as "Won't Fix" but please know that we'll be reviewing these issues as we begin planning for our next release. Thanks again for the great feedback, and keep it coming!

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Smart move... by Domien Holthof

Since this is a an issue that will be verified when the official version is released, there's a strong probability it will implemented... :)

How about 3-year release cycles? by Kevin McFarlane

Personally I think VS is so complex that they should move to a 3-year rather than 2-year release cycle. There should also be more than two betas, especially so when they introduce a major revamp like they have done for VS 2010 with its WPF shell. Whenever they introduce a change of paradigm like this it always takes them a few releases to get a solid version. Remember the transition from VC ++ 4 to 6? 4 was very ropey. 6 was solid and their best IDE to date in terms of stability and polish.

Re: How about 3-year release cycles? by chris barrow

Agreed. A 3 year release cycle would do everyone some good.

Response to: VS 2010 Bugs Being Ignored? by DJ Park

Since I’m the original poster, I figured I should jump in here :). I apologize if my responses made it seem like we are no longer fixing minor issues on VS 2010. In fact, the main focus for the VS and .NET teams at this point in the product cycle is to fix bugs and do performance work in order to deliver a high quality release. To support this, we are making a conscious effort to focus on bugs and performance rather than new features or functionality. The decisions made around the EnvDTE bugs were targeted decisions and should not be taken as a broader indication that we are no longer fixing bugs.



To shed some light around the decisions regarding these C# code model bugs, the main reason we decided not to fix these issues is because we are making longer term investments in a public language model. This API will do a much better job than the existing Code Model in surfacing our compilers and will provide a richer representation of code. As a result, we decided to limit our investment in EnvDTE/CodeModel and treat regressions of existing functionality with higher priority. The bugs in question, while important, existed in previous releases.



Thanks,

DJ

Re: Response to: VS 2010 Bugs Being Ignored? by Tom Moriarty

Am I the only one who has a problem with some of the terms / descriptions used here?

like Remember the transition from VC ++ 4 to 6? 4 was very ropey. What is a ropey transistion??

or This API will do a much better job than the existing Code Model in surfacing our compilers. How do you surface a compiler?? Is this like exposing, or is it like plastering?

TM

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

5 Discuss

Educational Content

General Feedback
Bugs
Advertising
Editorial
InfoQ.com and all content copyright © 2006-2014 C4Media Inc. InfoQ.com hosted at Contegix, the best ISP we've ever worked with.
Privacy policy
BT