The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted 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!
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Agile Maturity Model Applied to Building and Releasing Software
Case Study: IBM's Agile Transformation
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
Since this is a an issue that will be verified when the official version is released, there's a strong probability it will implemented... :)
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.
Agreed. A 3 year release cycle would do everyone some good.
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
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
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
5 comments
Watch Thread Reply