What’s next for Visual Studio and .NET FX?

It has been about 10 months since we shipped Visual Studio 2008 and .NET FX 3.5.  The team has been working on a couple of things since then – we shipped SP1 for both VS 2008 and .NET FX 3.5 earlier this Summer.  In parallel, we have been planning for the next wave of product releases and start development on the same.

I want to start sharing with you our vision, focus and priorities as we get full steam into developing the next wave of products – Visual Studio 2010 and .NET FX 4.0.

At a high level, here are the key areas that we are focusing on with Visual Studio 2010 and .NET FX 4.0:

·        Significantly improve the core pillars of the developer experience

·        Support for the latest platforms spanning the client, web, server, services and devices

·        Targeted and simplified developer experiences for different application types

·        Architectural improvements to the tools platform for better modularity and extensibility

These pillars are designed specifically to meet the needs of developers, the teams that drive the application lifecycle from idea to delivery, and the customers that demand the highest quality applications across multiple platforms.

Our commitment to customers is simple: To provide a consistent and simplified programming experience, regardless of the type of application being built.

Today I want to discuss the challenges faced by teams developing applications and the way in which Microsoft is meeting those challenges through our Visual Studio family of products and the .NET Framework. Specifically, I want to focus on our Application Lifecycle Management tooling, Visual Studio Team System 2010.  Over the next few months, I will talk more about other aspects of these products and what we hope to deliver with them.

The marketplace has begun to mature and accept ALM (Application Lifecycle Management) as a proven discipline for creating high quality applications in a reliable fashion. However, existing solutions in the marketplace have not kept pace with the changing needs of technical users and the expanding inclusion of non-technical users as part of the lifecycle. Visual Studio Team System 2010 will address the needs of these customers with a robust and streamlined solution.

Every customer today faces a similar set of business problems. These are:

·        How do we build high quality applications that deliver real business value?

·        How do we embrace the Application Lifecycle Management model effectively?

·        How can we ensure that all members of the team – both technical and non-technical – are part of the process?

·        How can we get the most value from our existing code assets?

·        How do we make powerful modeling tools available to everyone in the application lifecycle?


Our ALM tooling specifically addresses these questions and helps customers create high quality applications that deliver value to the business.  We will embrace the needs of all the users in the lifecycle – from architects to developers, from project managers to testers, and from idea to delivery – and provide tools that they can all use as needed. Key to a shared understanding of the application is the use of modeling tools. In essence, we are democratizing architecture by simplifying modeling, integrating it into the work of the participant in the lifecycle, and ensuring that models – the architectural artifacts – are available, accessible and valuable for every role in the lifecycle.

This is unique because we are delivering tools that integrate into the familiar IDE for developers, but also provide an approachable interface for less technical users, both on the Web (for work items) and in a rich WPF client (for the generalist tester). Likewise, our lifecycle management capabilities provide unified work item tracking, a web-interface, and dashboards that are available to everyone. Unlike many other tools, our work item management and reporting tools easily integrate with familiar applications like Microsoft Excel.

Two specific deliverables here will drive the next generation of ALM. First, our modeling tools have tight integration into the actual code of the application. This means that a developer or architect can use models to enforce constraints on code, as well as use models to explore existing code assets. Individuals can enforce a constraint in the architecture by allowing the tiers of a multi-tier application to talk to each other. For example, when an architect designs a system where the presentation layer should not talk to the data layer, you want to be able to enforce that model at check-in. VSTS 2010 can do that. We will be telling you a lot more in the coming months about our approach to modeling and why we believe it is critical in building the next generation of quality software applications.

Another key element here is being able to explore and re-use existing code assets. Only 20% of the code in most business applications is “new” code. The remainder is code that already exists and was written by someone else, possibly for something else, and definitely with less than adequate comments. Our modeling tools give developers and architects the capability of creating a full architectural picture of those assets, understand how they fit together, understand how they “work” and then make their re-use (or discard) that much easier. We are confident this will save time, resources, and ultimately deliver higher-quality applications.

This is just the beginning.  In the coming months, I will share with you more about the features coming in this next wave of products. 


Comments (41)

  1. Daniel Moth says:

    Visual Studio 2010 and .NET Framework 4.0

  2. Visual Studio 2010 and .NET 4.0 first news…

  3. Σήμερα η Microsoft παρουσίασε, για πρώτη φορά, την επόμενη έκδοση των εργαλείων και της πλατφόρμας ανάπτυξης,

  4. Ben Voigt [C++ MVP] says:

    As a C++ developer, I’m saddened by the death of the "10-is-the-new-6" mindset.

  5. caywen says:

    The feature I’d really love is the ability to develop iPhone apps on VS2k10.

  6. Sebastin says:

    Excellent article – address both developers and management alike!!

  7. Douglas says:

    Ben in what way? only announcements made today relate to the bigger picture not the individual languages. And the Topic is still there for PDC.

  8. Visual Studio 2010 et .NET Framework 4.0

  9. rory becker says:

    Is .Net 4.0 going to involve a new clr or will this be compatible with clr v2.0?

  10. tcmaster says:

    An answer to ur title: fire the editor team and by R# 🙂

  11. Torin says:

    What would be fantastic in .NET 4.0 would be a .NET classes designed to interact with an Exchange server without having to rely on Outlook or a Logged on user’s Mail profile.

  12. It’s true! Finally we got the official information from Microsoft on the next version of Visual Studio

  13. Tim Ng says:

    It’s been a long time since I’ve posted : we’ve been very busy working hard on the next version of Visual

  14. Leo en varios blogs como este , o este otro (en inglés) o la nota de prensa oficial (también en inglés

  15. lazy says:

    i will wait for vs.net 2012 and .net 6.0

  16. Gunther and I have been blogging about several of the new features that are coming in Visual Studio 2010

  17. Ben Voigt [C++ MVP] says:


    A goal of "Support for the latest platforms spanning the client, web, server, services and devices" sounds like the same old ignore-native-development-in-favor-of-whatever-we’re-calling-COM-this-week.  The word "native" doesn’t even appear in the post.  It’s all about "multi-tier" business logic and no effort enabling efficient close-to-the-OS tools, utilities, etc.  Taken together, this sounds like a significant shift away from the renewed emphasis on native development.

  18. David Campeau says:

    "Significantly improve the core pillars of the developer experience"

    Does this include properly supporting Multi-monitor scenario for the developper?

  19. Microsoft has provided the first look at the next version of its developer tools and platform, which

  20. Abhijit says:


    Is there a plan to support LINQ in C++/CLI

    This has been a bit of heartburn for us as we can’t get the C++ datastructures filled directly. Instead have to rely on writing a C# component which adds unwanted overhead….

    One option is to switch to C# but for that I will have to either find a new employer or …

    Please if you can gift us….

  21. Publicación del inglés original : Lunes, 29 de septiembre de 2008 8:40 AM PST por Somasegar Han pasado

  22. Hello Abhijit,

    We are not planning to support LINQ in C++/CLI. Our recommendation for your scenario is to use pure C# for the database layer and build an interop layer between your native C++ and your C# components (potentially using C++/CLI).

    Not supporting LINQ is part of the VC++ team’s strategy to focus on the two areas where we find most C++ usage and where we can bring the most value for the majority of C++ developers on Windows: 1) pure native development and 2) writing interop layers between native C++ and plain managed (C#/VB/…) code.

  23. Somasegar says:

    Thanks for the questions/comments about VS 2010 and .NET FX4.0.

    As we firm up our plans we will provide more details about the products in the coming months.


  24. Tomal Zaman says:

    Please do not complicate the VS 2010 as VB.net was (from Vb6 to Vb.net).

    Will it make life easier for business application developer: (who usually do not need academically correct programming methodologies. Managers are mostly interested in the end results (not polymorphism or OOP or SOAP or such confusing acronyms)).

    Ideally it should have robust form generator from tables/views/master-detail etc. (Yes there are lot around, creating more complications, Microsoft provided would definitely better unless Anti-trust will not haunt VS 2010)

    Easy report builder, with better cross tab reporting

    Easy built-in query builder (LINQ or SQL), which can be user fronted too.

    DB connection wizard

    Simple deployment (yes easier than Clickonce)

    Can it be OS neutral?!!! If it is not too much:)

    Anyway VB 2008 is excellent, feeling the vb6 days again.

  25. Peter says:

    "These pillars are designed specifically to meet the needs of developers, the teams that drive the application lifecycle from idea to delivery, and the customers that demand the highest quality applications across multiple platforms."

    Will you therefore consider adding the "Keyword Expansion" feature to Team Foundation Server?

    The DBAs that I work with (those that look after delivered, production SQL code) are reluctant for the whole team to move to TFS, because TFS does not allow them to embed version keywords into source code files. They want (!) to remain on Visual SourceSafe because of this.

  26. Byron says:

    Ditto what Douglas said.  I’d love to see an announcement for a new version of Visual Studio that doesn’t mention databases or N-tier applications.  It seems like Visual Studio just keeps moving farther and farther into a very specific niche application space:  database-driven websites.

  27. bharry says:

    Peter, I’m the Product Unit Manager for Team Foundation Server.  Keyword expansion is on our back log and is a feature we’d like to implement.  It’s unclear when we will get to it.  We get occasional request for the feature but more requests for others – which is part of why we haven’t gotten to it yet.  The other reason has to do with the difficulty of implementing keyword expansion in TFS.  There are two things that lead to the difficulty:

    1) Some of the information that needs to be put in the keywords (change set, for example) is only known by the server during the commit of the checkin transaction.

    2) The client compresses all files to send to the server (so save network bandwidth, server CPU cycles and server disk space) and the server doesn’t decompress them as part of the checkin transaction.

    So there are 3 approaches to implementing it and they all have some downsides:

    1) Have the server do it on checkin – requires decompressing, updating and recompressing all of the files.

    2) Have the client do it before checking – doesn’t have all of the information for all of the keywords.

    3) Have the client do it on dowload – requires the server to send the keyword info on every download operation so the client can do the expansion.

    Anyway, probably more info than you wanted.  One question I have that might help here, is which keywords are the most important to you?  There are some keywords that are easier for us to do than others.


  28. My favorite links from the 1:1st week of October 2008

  29. All the details – direct from Soma’s blog : What’s next for Visual Studio and .NET FX? It has been about

  30. Peter says:

    Brian, thank you for responding about keyword expansion. No, I’m happy with that level of information. Good explanation.

    Currently, my DBA colleagues rely on the SourceSafe keyword "$Header: $" which embeds file, revision, date, and author.  Personally, in TFS, I’d be happy with just changeset number, because I could determine everything else from that.

    In researching this, I noticed that the VSS help file states: "Because keyword expansion requires VSS to scan each file for keywords, it can considerably slow the Check In and Add Files commands." This is not something that any keyword expansion enthusiast has ever pointed out to me before…but then they wouldn’t, would they? 🙂

  31. [原文地址]: What's next for Visual Studio and .NET FX? [原文发表时间]: Monday, September 29, 2008 8:40 AM 从我们发布

  32. Last week, the VP of the Developer Division at Microsoft announced the next version of Visual Studio

  33. Toby says:


    Bring on VS 2010, MS is getting it done.

    .Net 4.0 is going to re-define programmatic conventions, creating new application scenarios.

  34. Ted says:

    .NET 4.0 should have improvements in file types handled especially standard media types (mpeg1, mpeg2, mpeg4, mp3, jpeg2000).  For example, a basic .NET wrapper to determine the running length of a mpeg2 file.

  35. My favorite links from the 1:1st week of October 2008

  36. Publicación del inglés original : Lunes, 27 de octubre de 2008 12:09 PM PST por Somasegar Este año PDC

  37. cisjokey says:


    Thanks for that, you just saved my day.

    You should read the post from;

    Tomal Zaman



  38. Andrea Loleo says:

    Does VS10 and .NET 4.0 provide the capability to host the new WF Designer on aspx pages?

    Is there any support to BPEL language (in terms of dedicated WF activities)?

  39. Pravin Indurkar says:

    Hi Andrea,

       Regarding WF activities for BPEL we are evaluating BPEL activities and tools as part of our post .NET 4 planning.  As with all features, we will use customer feedback to shape and prioritize the work.

    As for rehosting the WF designer in aspx pages it is not possible currently. The WF designer is a WPF control and can be hosted in a WPF application.


    Pravin Indurkar

  40. artur ferreira says:

    no puedo descargar

Skip to main content