Desmond File

Blog archive

Wonking Windows Live

If you're like me, you've been alternately hopeful, disappointed and downright dismayed by the uneven progress around Microsoft's Live efforts over the past year or so. A lot of it, I think, comes from the cart being thrust a couple hundred miles in front of the horse.

After all, who can forget the relentless over-branding of Live, which produced an utterly opaque clutter of online sites and services? Like the senseless .NET mania that infected nearly every Microsoft product launch in 2001 and 2002, the panicked rush to slap a Live sticker on every new Web offering served one effective purpose: to confuse customers.

It honestly worries me that a strategic software company like Microsoft can let itself fall prey to irrational brand exuberance. But it happens.

So imagine my relief upon hearing Microsoft Chief Technology Officer Ray Ozzie lay out a strategic Live platform vision to an assembled group of industry watchers at the annual Microsoft Financial Analyst Meeting in Redmond last week. Ozzie details a four-level platform that defines Live, finally providing a common ground for all Live products and services. The four levels are:

  • Global Foundation Services: The hardware and data centers that support and deliver sundry Web services
  • Cloud Infrastructure Services: What Ozzie called the "utility computing fabric," this layer enables critical app management, load balancing and deployment activities
  • Live Platform Services: A common layer of application services such as communications, identity management and (notably) the advertising platform infrastructure
  • Live Applications: The customer-facing software and interfaces that enable everything from creating and sharing documents to advertising

You can read the report from RDN News Editor Chris Kanaracus here.

The good news is that everyone in Redmond crafting Live services and products should now be working toward a common target -- a far cry from the disjointed efforts we've seen to date. And all those efforts should tie neatly into the growing body of Software-plus-Services work that will be so critical moving forward.

The bad news? We're 12 to 18 months from seeing Microsoft deliver a coherent foundation for corporate developers to build against.

For now, it's time to watch, learn and prepare as Microsoft finally starts working toward a workable vision for the Live platform.

What do you think of Microsoft's plan? Do you have any advice for Microsoft as it starts forging a framework for its fledgling Live platform? E-mail me at

Posted by Michael Desmond on 08/01/2007 at 1:15 PM

comments powered by Disqus


  • Purple Blue Nebula Graphic

    How to Compute Disorder for Machine Learning Decision Trees Using C#

    Using a decision tree classifier from a machine learning library is often awkward because it usually must be customized and library decision trees have many complex supporting functions, says resident data scientist Dr. James McCaffrey, so when he needs a decision tree classifier, he always creates one from scratch. Here's how.

  • Blazor's Future: gRPC Is Key

    Blazor guru Steve Sanderson detailed what Microsoft is thinking about the future of the revolutionary project that enables .NET-based web development using C# instead of JavaScript, explaining how gRPC is key, along with a new way of testing and a scheme for installable desktop apps.

  • Don't Do It All Yourself: Exploiting gRPC Well Known Types in .NET Core

    If you're creating business services that send dates and decimal data then you may be concerned that gRPC services don't support the relevant data types. Don't Panic! There are solutions. Here's how to use them.

  • Sign

    Microsoft Points Blazor to Native Mobile Apps

    Blazor, the red-hot Microsoft project that lets .NET developers use C# for web development instead of JavaScript, is now being pointed toward the mobile realm, targeting native iOS and Android apps.

  • Circl

    Implementing State in .NET Core gRPC Messages with oneof

    In the real world, you've been dealing with the State pattern every time you designed a set of database tables. The Protocol Buffers specification lets you do the same thing when you define the messages you send and receive from your gRPC Web Service.

.NET Insight

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.

Upcoming Events