Windows Vista developer story

Over the course of Microsoft’s history, there have been a few seminal events that enable a whole new generation of applications such as the launch of Windows 95 and the advent of the .NET Framework.  With the impending release of Windows Vista and the 2007 Microsoft Office System, we have a big opportunity for developers to create the next generation applications with new user experiences and seamlessly connect to other systems. 


Over the next several months, I am going to blog regularly about some of the new scenarios and features that developers will see in these two families of products.


I want to start out by pointing out some of the new technologies that are included in Windows Vista.  We’ve talked extensively about some of the great technologies coming in the .NET Framework 3.0 which is a part of Vista.  I am very excited about the new user experiences that you can create using Windows Presentation Foundation and the new ways that you can connect applications using Windows Communication Foundation and Windows Workflow Foundation. 


Here is a trivia for you.  We have added more than 7,000 new native APIs for Windows developers in Windows Vista.  Examples of some of the exciting new areas where we have exposed new APIs include the new integrated search capability and the new peer-to-peer functionality.  To get the whole story, please check out the Windows Vista Developer Story at the Vista Developer Center.


While Windows Vista will provide a tremendous number of new technologies, the team has worked to make this highly compatible with previous versions of Windows.  If you haven’t already started, now is a great time to start testing your applications on Windows Vista.  You can find a lot of details on how to do this on the Developer Readiness Center.  This will give you information on things that may have changed under Vista, how you can make your application perform well with User Access Control and ways to enable your application to take advantage of the new functionality.



Comments (14)

  1. Interesting!

    Now about the 7,000 native APIs. They must be either Win32 or COM. Unmanaged.

    What’s the plan for the managed view for those new APIs? Orcas time frame?

    Till then, should we go DIY or will there be PIA?

  2. J. Ackass says:

    I thought Vista was gonna be simplified?

  3. says:

    Sure sounds like it is going be another insecure, unstable software product from the company that brought us Windows ME and Outlook

  4. E’ sempre iteressante leggere i post di Somasegar. Non sono tecnici (lui è Corporate VP), ma danno sempre…

  5. tomarcher says:

    <<< "I thought Vista was gonna be simplified"

    From a dev point of view, I think it’s a misnomer to equate more APIs with compexity or to assume that more APIs and simplicity are mutually exclusive.

    In reality, more APIs simply means easier, documented access to operating system abilities that either didn’t exist before or that had to be customer developed (or purchased) by the dev/customer.

    Therefore, from the perspective of accessing functionality that either didn’t exist before or was difficult to achieve, the new native APIs make it markedly easier to develop for Windows Vista than previous versions of Windows.

  6. Dave Jewell says:

    << In reality, more APIs simply means easier,

    << documented access to operating system abilities

    << that either didn’t exist before or that had to be

    << customer developed (or purchased) by the

    << dev/customer.

    Wrong.  The one thing we can say for sure is that more API’s means more complexity.  Why?  Because those API’s are added to the thousands of API’s that already exist.  x+7000 gives a number greater than ‘x’.  Go figure.  

    Hopefully, Microsoft will have documented these API’s well, and hopefully they will have had the sense to provide an object oriented interface to these API’s even for unmanaged coders.  But none of this is certain.


  7. tomarcher says:

    Norman: Sorry to take so long in responding, but I wanted to confirm. There are efforts to make sure that many of the most common scenarios and experiences in Vista are supported by managed code APIs.  However, that doesn’t necessarily extend to create managed equivalents for all of them.  Are you concerned only about stuff related to BCL types or other scenarios (e.g. file open dialogs and Winforms)?

  8. Cyphorous says:

    Well. I m new at developing with the .NET Technologies. But it sure sound interesting with the size of the APIs. But i would definitely suggest that they should be properly documented.


  9. tomarcher says:

    Cyphorous – Each team’s UE (User Experience) department is hard at work doing just that. In addition, Intellisense files are constantly being updated in order to aid in developing applications with editors that support Intellisense – such as Visual Studio 2005.

  10. chan says:

    Nice one…

  11. magicbean says:

    >>We have added more than 7,000 new native APIs for

    >>Windows developers in Windows Vista

    i wonder what it takes to publish that 7000 APIs. It’s 7000 end-developer functions and methods!

    there’s about 1200 header files in sdk for vista. so it’s about 5.8 new functions for each header file.

    is this a joke?