* Latest Microsoft developer framework could lead to fewer help desk calls by end users
One of the promises of the next versions of Windows – Vista on the desktop and whatever Microsoft will officially name the Longhorn server – is the .Net 3.0 framework. Software built with this version of the framework will run on currently shipping versions of Windows, but it will run better on the next versions and, perhaps more importantly, it will ship with them (see “Microsoft .NET Framework 3.0 Deployment Readme” for what’s involved in deploying it to an existing platform).
The new .Net is divided into four major areas, called “foundations”:
* Windows Workflow Foundation.
* Windows Communication Foundation.
* Windows CardSpace.
* Windows Presentation Foundation.
Each is either new or has greatly enhanced functionality.
Windows Workflow Foundation (WF) creates a workflow engine. A “workflow” is similar to a programmer’s flowchart, but usually contains business logic. Rather than creating thousands of lines of programming code, WF allows you to specify actions to be taken, rules to be followed, prerequisites (that is, steps that must complete before another step can occur). Each step is an activity executed by the WF engine. Activities can be reused in different workflows so that libraries can be built up. Microsoft’s upcoming applications (Office 2007 and Windows SharePoint Services, for example) will use WF establishing a rich library of activities that others can draw on. This will also mean that applications and services will tend towards similar behavior in any given circumstance or context leading to predictability, something every network manager would love to have.
Windows Communication Foundation (CF) consolidates the various communications methods used between and among applications, services, operating systems, network nodes and networks. CF provides a middle layer that gives programmers a unified application programming interface to write communications code then attaches it to whatever communication method (SOAP, HTTP, Microsoft Message Queuing, etc.) might be used in a particular communications transaction. This is similar to the abstraction at the network layer that occurred 20 years ago when programmers no longer had to write code for each specific Ethernet, Token-Ring or Arcnet card and could, instead, simply write to a network interface layer which translated through a specific driver to each card. This should reduce the incidence of hard to find communications errors.
Windows CardSpace (formerly called InfoCard) is perhaps the most widely publicized of the new foundations. This card-like metaphor is used to present identity data and credentials to requesting parties (applications, services, Web sites) under the control of the user, providing for better simplified sign-on as well as better user control of the dispersion of identity data.
Windows Presentation Foundation (WPF) is all about the user interface. Microsoft, over the years, has shown a consistent drive to standardize the user interface for all applications and services. How often, for example, do you simply hit “F1” to bring up a help screen without first having to check to see if the program supports it? As explained in the white paper “Introducing the .NET Framework 3.0”: applications “need to display video, run animations, use two- and three-dimensional graphics, and work with various kinds of documents. And all of this must be possible whether the application is accessed from an installed desktop client or through a Web browser.”
WPF makes it easier for programmers to create a consistent experience across multiple platforms, applications and video presentations, leading to a more consistent user experience and, hopefully, fewer help desk calls.
That may be all you need to know. If not, read the whole white paper which, while intended for programmers, is very readable and quite informative. You just might discover that the next round of operating system upgrades could pay benefits for you.
