Visual Studio 2010 momentum

Since we launched Visual Studio 2010 and .NET 4 on April 12th of this year, it has been exciting to see the extremely positive response to the product.  Within six months of the launch date, Visual Studio 2010 usage surpassed all other previous versions of Visual Studio based on usage data collected from customers who opted into sharing their usage data with us.  This is the fastest adoption of a new release of Visual Studio ever, and we are seeing continued strength in the adoption of Visual Studio 2010.

Visual Studio 2010 SP1 Beta

Since the release of Visual Studio 2010, we've been working to address high priority issues you've brought to our attention through forums like Visual Studio Connect.  We've also focused on improving the overall experience in a few important areas, such as unit testing, support for GPU acceleration in C++ applications, and offline help.  You can learn more about the work we've done in SP1 on Jason Zander's blog.

Today, MSDN subscribers can download and install the beta of Visual Studio 2010 Service Pack 1 from this site.  If you're not an MSDN subscriber, the download will be available on Thursday, December 9th here.  I encourage you to download it and try it out.

Your feedback on this release will help us improve the final release.  Please report any issues you come across in the SP1 Beta to Visual Studio Connect.  Once you've had a chance to use Visual Studio 2010 Service Pack 1, please also give us your feedback by taking the Service Pack 1 Beta Survey.  The results from this survey inform our work so we build an even better SP1 RTM.

Team Foundation Server 2010 and Project Server Integration Feature Pack Beta

Also available today for MSDN subscribers is Visual Studio Team Foundation Server 2010 and Project Server Integration Feature Pack Beta.  This feature pack enables sharing project status and resource availability between team members using TFS and Project Server. The feature pack beta's "go-live" license allows customers to deploy it in their production environments.  You can learn more about the feature pack on Brian Harry's blog or download the feature pack beta from MSDN.


Comments (25)

  1. grumpy says:

    Yes, it certainly seems to have a lot of momentum. Once it's been running for a while, it, takes *minutes* to close. And similarly when launching, there's obviously a lot of inertia to overcome.

    Oh, that wasn't what you meant?

  2. Jon says:

    Congratulations to the VS IDE team for making this version even slower than VS2008 for C++. You guys never fail to disappoint us with your commitment to performance regression for each new version. VS2010 isn't the new 6, but maybe VS2012 will be _almost_ as good as your 12-year old IDE?

    See the comments here for a bunch of feedback which I'm sure will be ignored.…/microsoft-tells-what-s-next-on-c.aspx

  3. mark gordon says:

    Good Afternoon Soma,

    I totally agree the momentum is building I have never seen a development tool lose productivty as fast as Visual Studio. Backward momentum Rocks!

    With every release of Visual Studio Microsoft is getting closer to matching the productivity and performance of punch cards. I guess there is nothing wrong with small websites that require 500,000+ lines of code to write if you are using MVC, that is so worth getting close to the metal!

    There is also a lot of momentum when it comes to switching paradigms and technology every couple weeks. Man I just love the momentum generated by staying on a constant learning curve.

    Mark Gordon

  4. Shawn B. says:

    Wow!  The negativity and pessimism towards Microsoft increases every day.  I do not experiance such issues with Visual Studio 2010 Ultimate that everyone else complains of — but in full disclosure, I do not work with C++.  VS 2010 has been wonderful.  We use solutions with over 100+ projects and while I admit, the memory limitations of WinXP and VS 2010 can become annoying, the IDE itself is pleasant to work with.  Just use the "Solution Load Manager" extension and things work out just fine.

    I look forward to the Service Pack.  Keep up the good work!

  5. Steve says:

    In terms of web-development the innovation in Visual Studio is non-existent. Microsoft is merely attempting to mimic the open source tool chest.  PHP compatibility, MVC,  JQuery and Javascript are not new, where is the wow factor in plagiarizing a technology for inclusion in Visual Studio?

    On the rare occasion Microsoft releases something remotely interesting it seems the technology doesn’t even reach maturity when development is stopped, WPF, Ajax Toolkit, POPFLY, LINQ TO SQL and soon to be SILVERLIGHT all fall into that category.  Given how Microsoft technology is trending no one should make a major investment in any of Microsoft’s new BETAWARE. Visual Studio is quickly evaporating into a stale cumbersome enterprise CTP development environment.

  6. anirudha says:

    great news ! tell me the difference between service pack 1 beta and feature pack 2.

  7. phuff says:


    We're very interested in tracking down issues like the launching and shutdown issues you mention.  Please open a bug report on this issue in Connect at


    Polita Paulus


  8. S. Somasegar says:


    Feature packs are extensions to Visual Studio that add new functionality in specific areas.  Feature Pack 2 adds testing capabilities to VS such as playback of test cases in Firefox and the Coded UI Test Editor.  It also adds modeling features for UML diagrams and creates dependency graphs between C, C++, and ASP.NET projects.  You can learn more about Feature Pack 2 here:…/gg269474.aspx

    Service packs are in-place upgrades of Visual Studio bits that address high-impact issues across the product and may also add limited features.  Service Pack 1 Beta has the features listed above, and also addresses issues within Visual Studio that have surfaced since we released VS in April.  We highly recommend that customers install final versions of service packs, but feature packs are purely optional.


  9. Marcello says:

    I am using UltraEdit and the command line… Thank you anyway.

  10. G.T says:

    I wrote a long replay, but my wife asked me don’t criticize people, so to make it short, VS.NET 2010 is slow, please improve its performance for the future developers, for me it is too late, I am moving Client Side development to Google Chrome (runtime, debug, and edit), it is hundreds of times faster than WPF/C# 4.0 and single threaded 🙂

    For everyone else, there is .NET and Java, very slow, and dinosaurs

  11. Marcello says:

    It there available a list with all the fixes that are included in this service pack?

    I would like to know if this problem has been fixed:

    <a href="…/statically-linked-mfc-applications-are-massive">Statically linked MFC applications are massive</a>

  12. phuff says:


    We are planning to post a list of the Connect bugs fixed in the beta for SP1.  I will post the location of that list here when it's available.

    Polita Paulus


  13. Jim says:

    Agree w/slowness – could you post something on what could be done to improve performance.  I use a lot of third party components since the out of the box stuff sucks.  Oh sure,  I could make the out of the box stuff good, but then I wouldn't get any work done for the customer that pays the bills.  When I run an website in debug mode,  it says "Loading… (insert differnt librarys/components)" It does this EVERY TIME.   Also deployment sucks – how about a DropBox type deduplication type deployment for the 2 characters that I change but required a 15 minute deploy (even if just to check versions from xcopy/d) to find out NOTHTING has really changed!  Could/would some type of ramdisk help?

  14. Tom says:

    At our company we use Visual Studio 2010. Unlike what others claim here, it starts and shuts down extremely quickly and we have not faced any performance issues. We use C# and VB.NET – no problems at all. Those who are complaining – are you using Windows XP? VS 2010 works lightning fast with Windows 7 and Windows Server 2008 R2. No complaints about the WPF interface.

    However, I do agree with some people here who claim that Microsoft pulls out of their own technologies quickly and its difficult to understand what may be thrown out next. Why was Ajax Toolkit discouraged and why did you start touting jscript all of sudden? Just because of open source pressure or that they out-witted you guys? Why are you guys promoting MVC. What is the problem with regular way of doing ASP.NET sites? Do you have scientific or statistical proof that MVC is better than the original approach? How many .NET developers actually use MVC? MVVM for Silverlight – why is not fully supported (if in fact its purpose was to make development easier!) Why did you guys discourage LINQ-To-SQL and started encouraging Entity Framework? The former is so much easier to use and with some more work from Microsoft would have more adoption than EF.

    Lot to think about…

  15. Guillaume Roques says:


    When we think developers that are consuming Ajax it breaks into two segments:

    a) Developers that want to write some client side script in their pages.

    b) Developers that want their applications to automatically take advantage of Ajax functionality.

    Our investments into jQuery are targeting people in the first batch while the Ajax Control Toolkit and the rich server controls offered by third party vendors target people in the later case. We think there are developers in both of these segments and are trying to target them both just like below in the MVC section you can see we are trying to target multiple types of developers. This isn’t about choosing one Ajax strategy over the other you can use one or the other or both together.

    With regards to MVC, we have had in the past one framework for developing Web Applications and that is ASP.NET Web Forms. This framework was designed to make the transition from developing desktop applications to developing server-based web applications very easy it also gives developers great benefits in productivity by letting them leverage rich web controls that have lots of built in functionality. While trying to grow the types of developers that can use ASP.NET we also identified the MVC pattern as a common pattern used by many other web frameworks such as Ruby on Rails and CakePHP and as a result we created ASP.NET MVC to provide a bridge to developers that like that pattern to be able to easily adopt ASP.NET and the power of the .NET framework and more generally our Web Platform. We are focusing on providing choices to various types of customers. We will continue to invest in all areas of ASP.NET (Web Forms and MVC).

    From a data perspective, ASP.NET works with any data solution in .NET but Entity Framework has been getting better and better with each release and with the release of EF Feature CTP 5 we think that it is very compelling for web data scenarios and are working to provide more guidance on how to use it.


    Director of Product Management – Microsoft

  16. Carlos says:

    Mark Gordon on his blog said he left comments to you. Can you please post comments with your reply. I like to know your view, it would help VFP developers. Thank you

  17. Somasegar says:

    Mark Gordon:

    My blog isn’t moderated and comments should show up within a couple minutes of posting.  Sometimes MSDN’s automatic spam filter triggers on blog posts, as it seemed to have with yours, so I’m posting it here:

    @Guillaume You wrote "target multiple types of developers." There was a type of developer that "used" to be able to deliver cost effective solutions to our clients with 10-50 users using visual foxpro or visual basic. We were able to distribute custom solutions to our clients without having the burden of eating licensing costs or charging them money to write massive amounts of plumbing code that is required using VS.

    Further, FoxPro was a mature product permitting business owners to make a significant investment in training their developers without being concerned about ROI. Which is a significant concern with your current trends especially for web development. We also could develop solutions quickly due to VFP'S robust object model with a functional class browser, RAD tools and more importantly a data centric language all of which are absent or useless in Visual Studio.

    Given it is not possible in Visual Studio to generate a lan database application faster (I am willing to defend this statement as I have done in the past if needed) with the same or lower cost of ownership then VFP, my question is what is your plan to target that "type of developer"?

    With all due respect, the only path I see which is on target for those "type of developers" unfortunate enough to fall into this category is moving to MySql, Open Source and continue to use VFP for desktop application solutions. This is a lesson I learned too late in the game.

    Perhaps instead of trying to cater to/attract the open source MVC developer don't you feel it would be wise to first address the needs of your current/former customer base that was orphaned when VFP and VB received their end of life?

    Basic business 101: it is much cheaper to retain a client then it is to attract a new one.



    Mark, I do want to tell you that I hear your concerns.  You are passionate about Visual FoxPro, which is great.  We will have to respectfully agree to disagree about Visual Studio and .NET.  I hope we can lay this topic to rest.

    For all commenters, signing into MSDN with your LiveID before posting will help keep your comments from being filtered as spam.


  18. Tom says:

    Guillaume, please, all of you at Microsoft, keep in mind that the developer community of Microsoft is the single most important user base for you. How this user base grows is something you guys need to think about differently. Just by adding features from open source to attrack the open source developers is whether you like it not, a secondary concern (they will most likely never come anyway). You guys need to focus on Microsoft developers and keep the products focused – simple, light, fast and stop adding and dropping good new technology at the expense of using resources and money to attract open source developers.

    Again, how many developers use MVC please? Any stats? Any scientific proof this approach is any better than regular web forms way? Why would people find EF more attractive compared to LINQ-to-SQL is beyond me (if you guys had continued to invest heavily in adding missing features to it instead of EF). EF is way too complicated and way too much coding and setup is involved. Either simplify it or give solid videos/training to show how it works with ASP.NET, Silverlight and other technologies for the desktop.

  19. Carlos says:

    Thank you for posting. I would have liked more substance in your reply to Mark. There are many important points that are unanswered. Can you revisit this again. Thank very much you.

  20. Dean.J says:

    @Somasegar, will you please answer 2 questions truthfully: Why is there only 1 SP provided for Visual Studio 2005, 2008, and likely for 2010 as well?  Why after so much hype about a new version of Visual Studio, will MS pretty much sweep it under the rug and try hard to get customers to get the next version when it comes out?

  21. Mark Gordon says:

    Hello Soma,

    Thanks for the reply. I would like to make a slight correction to your reply.

    I am not passionate about Visual FoxPro as a product, I don't sleep in an I LOVE THE FOX t-shirt or have a FoxHead hanging in my office. There are things in VFP I would have like to have seen done differently. There are also a lot of things VFP does nicely, handling data and classes are a great example. It would have been advantageous to Microsoft to implement those ideas instead of dismissing VFP and attempting to reinvent the wheel and CONSISTENTLY missing the mark in Visual Studio, inclusive of 2010.

    What I am passionate about is "productive and stable" development environments and more importantly my "clients". I want to create software for my clients quickly and in a cost effective manner, two key elements missing in Visual Studio.

    There is a simple litmus test that should be given to a software development tool, can it develop the same core application functionality, at a minimum, as effectively as it's predecessor. Given not one person has developed a data centric LOB application in less code using Visual Studio compared to VFP, obviously Visual Studio failed.

    In closing I sincerely do appreciate your time.



    By the way: If I laid this topic to rest, you would miss me 🙂

  22. phuff says:


    We work hard to address the high priority customer issues in our service packs for Visual Studio and are proud of the quality of those service packs bring to Visual Studio.  We also continue to address customer issues both before and after service packs are released, and critical servicing fixes are released for products throughout their supported life.

    Different releases focus on innovation in the toolset for the changing underlying platforms.  For those that wish to build on new features of platforms or new platforms, such as Windows Phone 7, we often offer free versions of the toolsets (like the Visual Studio Express editions) so developers can use the most current toolsets to build applications.

    Polita Paulus


  23. phuff says:


    Jason Zander has published a list of some of the issues fixed in the Visual Studio 2010 SP1 Beta.  You can find it here:…/visual-studio-2010-service-pack-1-beta-feedback.aspx.

    Polita Paulus


  24. Marcello F. says:


    I downloaded and installed the Service Pack and I found the bug that I reported when VS2010 was released. I plan to migrate to VS2010 when this problem is fixed: I require this functionality for several of my projects.

    I posted the details in Connect when VS2010 was released in April.…/object-browser-doesnt-display-inherited-members-functions-and-variables


  25. Marcello says:

    Inherited members (public, protected, are not displayed in the class view and object browser for C++ projects. Without a doubt, this bug hasn't been fixed yet.

Skip to main content