Tracking change and innovation in the enterprise software development community
Free Book Offer
SOA Demystified
$40 Value
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
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!
Right Collaboration Architecture Drives Business Transformation
Testing C# and ASP.NET, w / Ruby, Noda Time, .NET State of the Art - AlphaGeeks Track @QCon London
Regaining control of the data centre
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
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
5 comments
Watch Thread Reply