S. Somasegar is the corporate vice president of the Developer Division at Microsoft. Learn more about Somasegar.
In October, we shipped Beta 2 of Visual Studio 2010 and .NET Framework 4. Since then, we have received a lot of helpful, constructive feedback from you all. Thank you.
A lot of you have given us very positive feedback on the new capabilities of VS 2010 and .NET Framework 4 and are very happy with the breadth of value that we are poised to deliver in this release.
At the same time, you have also given us feedback around performance issues, specifically in a few key scenarios including virtual memory usage. As you may have seen, we significantly improved performance between Beta 1 and Beta 2. Based on what we’ve heard, we clearly needed to do more work. Over the last couple of months, our engineering team has been doing a push to improve performance. We have made significant progress in this space since Beta 2.
With these improvements in the product, we do want to make sure that they truly address the performance issues while continuing to maintain a high quality bar. As a result, we are going to extend the beta period by adding another interim checkpoint release, a Release Candidate with a broad “go live” license, which will be publicly available in the February 2010 timeframe.
Since the goal of the Release Candidate is to get more feedback from you, the team will need some time to react to that feedback before creating the final release build. We are therefore moving the launch of Visual Studio 2010 and .NET Framework 4 back a few weeks.
Please continue to send us your feedback. It truly has an impact on the product development process and helps us to deliver a high quality product.
Namaste!
That is really great news. Thank you for the extra feedback release
I appreciate this very much. We would all much rather have great software longer than lower quality software sooner.
Thank you.
Some of us use this product virtually every day. Keeping the performance level high allows us to concentrate more on our problems, not the tools themselves.
Looking forwards to the Release Candidate.
Thanks for working hard on getting this right.
As MS policy for servicing VS (buy new version) is different than for servicing Windows (go to Windows Update), I like the idea of delay :)
VS2010 seems to have a lot of redesign and this means that it was going to be buggy not only in Native and Smart Devices departments.
Really, MS should process public feedback on Smart Devices support in VS. This part has always been the buggiest part of VS and now we already saw two public betas without any Smart Devices support. The only other option is to move Smart Devices support into a separate installation package and release it as an add-on.
Good Microsoft has always been Improving itself.
This is one of its example.
I recently downloaded the Beta2 and found no time to check the new feature of it.
Thus now i got some more time, i can test and Check all its features
Great news, the current VS2010 beta version crashes too frequently (usually when editing XAML for me) to be a usuable product. Perf also needed work.
On the other hand the new features (with the exception of help which seems to be going backwards) are a great step forward.
I hope the release candidate will not be as buggy and Beta 2.
I has to be usable and stable!
The RC that you mention, ¿will include development for Windows Mobile? ¿Can you tell us how smart device's development is improved?
Thx!
It might be a good idea to update the VS2010 home page, which still has 22nd March as the launch date:
http://msdn.microsoft.com/en-gb/ee506597.aspx
I hope one day VS could reach the quality, performance and versatility of Nokia Qt SDK to finally ends as a valuable low cost alternative to Qt.
That is great that MS is taking the time to make it right in stead of releasing a product that will require a update shortly after it's realease.
I use VS2010 every day on production products. I love it! I have relatively few issues, but I am definitely glad they are extending it so we have a much more high quality product in the end. Thank you for the hard word!
Excellent decision. It will really help us to work with a more stable new version and really try to go live.
It's great to know you're taking into account all the feedback.
I'm really happy to know you understand developers and architects decided to extend the Beta period.
I have no doubt that VS 2010 will rock! However, it needs more work to improve the performance and solve some crashes that make it really difficult to work in complex projects.
Gastón C. Hillar
It's all good. How will the delay affect Azure people yearning to target 4.0 ... with heightened expectations for Feb/Mar timeframe? Should this affect them too?
My desire is that it shouldn't have to if you already have a code freeze on the CLR itself.
I hope it will let you improve link time. That's the only critic I have on the product, for the rest I think you made great improvement.
I agree that it's better to release later with greatest performance than sooner with slow link time. We will use this tool daily and if we can cut link time, it will increase our productivity.
There are some suggestions about that on connect, I listed some title below:
- "Optimize link time in real developers environment"
- "Slow link on vc2005, > 10 times slower than vc6"
- "Improve link.exe performance"