New Tools for Microsoft’s New OS

Capp · Aug 17, 2005

Microsoft’s next major desktop operating system, previously code-named Longhorn, has morphed into Windows Vista. Although the new OS isn’t slated for final release until late in 2006, Microsoft has already released a number of developer tools designed to give coders a head start on building next-generation applications. Get the jump now on Vista development: it’s not too early.

Developers, Take Note

Microsoft’s new developers’ tools focus on helping programmers build and test applications using WinFX, which is the set of next-generation application programming interfaces (APIs) that Microsoft is corporating into the new operating system. The tools, which are available for free download from Microsoft, include:

WinFX Runtime Components Beta 1, which provides a virtual environment within which Vista-specific applications can be tested. It includes versions of Windows Presentation Foundation, Windows Communication Foundation, and InfoCard—all key elements of the new OS—to allow for realistic assessment of updated code in the target environment.

WinFX Software Development Kit (SDK), which allows developers to create managed applications and libraries either from scratch or using a series of includes sample applications. It includes a range of documentation, code samples, command-line compilers, and tools, as well as .NET Framework 2.0.

Microsoft has built a new online resource, Windows Vista Developer Center. This site will serve as a centralized clearing house of tips and tricks for developers during the ramp-up to Vista’s release.

The software vendor is also including its Windows Driver Kit with the Vista beta code. WDK, which facilitates development of drivers for a wide range of hardware, will be updated with each successive beta release.

A Quick Look at Vista

Although Microsoft has removed a number of significant features—including the WinFS advanced file system—from the code base to ensure the final release ships by 2006, Vista nonetheless represents a fairly major re-think of the OS. Beyond the prettier user interface, Vista sports a re-thought security architecture that incorporates new rules governing who can do what on the system, when, and what happens when security parameters are violated.

Because so much has changed, developers will need sufficient lead time to ensure they are able to deliver apps that work effectively within—and take advantage of—the new environment. Some key new elements of the new OS include:

Windows Presentation Foundation (WPF): Formerly known as "Avalon," this is Vista’s new graphics and presentation engine. Microsoft’s initial overviews of WPF indicate a richer, more consistent interface that incorporates more modern elements of design and usage.

Windows Communication Foundation (WFC): This previously held the code-name "Indigo," and is a service-oriented messaging system that extends the existing .NET framework and integrates it more fully into the new OS.

Aero: The user experience guidelines for the new OS. It stands for Authentic, Energetic, Reflective, and Open, and it governs the look and feel of the new interface. Beyond simple looks, it defines how the end-user interacts with the system and how this influences workflow. This guide includes the Aero Wizard, which serves as a framework for building all new wizards, as well as the Task Dialog, which guides developers through working with Vista’s new error messages and prompts.

InfoCard: This system bolsters security by managing the end user’s personal information when interacting with external Web sites.

Some of these elements, like WPF and WFC, will likely be released as standalone products for installation on older versions of Windows. Regardless, their consolidated inclusion in Vista makes the new OS a very different animal than Windows XP or 2000. These fundamental differences between will necessitate a fundamentally new approach to application development.

Although the OS is still in early beta and large numbers of end users will not be using final versions of it for a significant amount of time, it is clear that the transition process has already begun.

Recommendations

Build a Vista development environment. On the assumption that Windows Vista already represents a target desktop OS environment for the organization, now is the time to start bringing developers up to speed in building applications for it. Download and install all development tools as they become available. Work with development communities like MSDN to get on beta lists for updated Vista code.

Update current software inventory. Impending OS rollover provides an excellent opportunity for IT to assess and refresh its software inventory. Work with business leadership to identify which applications will need to be retained, which ones can be retired, and which ones will require redevelopment to function in the new environment.

Assess developer skill levels. This is also an excellent time to review each developer’s training plan. Adjust future plans to allow for Vista-specific skills development. Seek training as it becomes available and incorporate successful completion into performance management processes.

Watch for more tools. Microsoft isn’t finished filling out its set of Vista development tools. Still to come is an application compatibility toolkit that will ship as part of the Vista Beta 2 package. This is a crucial element in ensuring applications written for earlier versions of Windows will function in the new environment. Microsoft’s release timing is in sharp contrast to its Windows XP SP2 experience, when it failed to deliver the compatibility toolkit until well after the service pack was released. This resulted in significant software incompatibility issues for customers.

Don’t jump too fast. Info-Tech strongly recommends against early and widespread adoption of Version 1.0 of any software release. Radically new code is usually mature enough for enterprise deployment only after it has gone through one or two additional significant revision cycles. This is especially applicable to major OS releases like Vista. At the very least, wait for the first Service Pack release, and start with a limited-scope pilot or test lab implementation to familiarize staff with the new OS.

Bottom Line

Every major new OS release drives a parallel effort by the development community to keep pace. As IT gets ready to evaluate Microsoft’s new OS, it must invest sufficient resources in bolstering its application development resources as well. Incorporate Microsoft’s new tools into current development practices and keep watching for updates as the Vista release date nears.
Click to expand...

Article

Log in or Sign up

New Tools for Microsoft’s New OS

Capp Registered Member

Log in or Sign up

New Tools for Microsoft’s New OS

Capp Registered Member

Useful Searches