What’s the future of the LHSDK?  We’re currently designing a system, code named “Vegas” to deliver the Longhorn SDK for Longhorn RTM.

 

Official Vegas Elevator Pitch:

 

  • Dynamic content updates at the developer desktop for major and out-of-band releases enabled through a componentized, real-time publishing model. 
  • XML content pushed to the developer desktop, resulting in a more powerful user experience and flexibility and richness in defining and updating user views. 
  • A rich client with subscription model allowing developers to selectively define how they want to access content (locally, online, etc.). 
  • Longhorn exploitive components in the rich client, including components that take advantage of Avalon, Indigo, WinFS and more.

 

Vegas is being designed and built via a glorious partnership with MSDN and SDK User Education teams around the company.

 

Usual disclaimer:  This is our vision.  We have not yet implemented this vision. Yet.  But we plan to (we’re writing specs furiously right now).  Your mileage may vary (and so will ours).  Hopefully our eyes aren’t that much bigger than our stomach on this one.  What was that saying about “…your goals being just beyond your reach…”?  I hope our arms aren’t too long…

 

Check our Hari Sekhar's blog at http://blogs.msdn.com/HariSekhar.  Hari is seeking input on the Vegas user experience.