Previous section   Next section

UNDERSTANDING THE .NET FRAMEWORK

The .NET Framework attempts to transform applications to online services that can be used over the Internet or in intranet environments. The underlying goal is to provide customized and comprehensive solutions to users regardless of a user's location or computer system. To achieve this goal, the server-centric approach to computing that currently defines the Internet must change. Another challenge is to break away from the concept of localized client-based applications. Looking into the future, a user should be able to log on to any system and get access to its data, applications, and even familiar settings. To realize this ability requires looking at applications and systems not as standalone entities but as services that are called on demand by the user. These application services could replace packaged software and be rented or leased over the Internet. Packaged software will probably not disappear, but Microsoft officials believe that this new model will radically affect the way businesses and consumers obtain up-to-date products and conduct business. Individual and corporate users conceptually will be able to get applications on demand through either a subscription or a rental arrangement. A prime example of how this could work is the automatic operating system update facilities provided by Windows XP and Windows Server 2003. When patches need to be applied, updates over the Internet can be applied automatically or interactively.

Foundation Technologies

The concepts underlying .NET are industry-standard technologies that should enhance its acceptance and interoperability. Microsoft believes that this approach is founded on the basic principles of common description, connection, communication, and discovery.

The eXtensible Markup Language (XML) is the centerpiece of the .NET strategy. This open standard is managed by the World Wide Web Consortium (W3C). Stated simply, XML changes the way in which applications talk to one another. It is designed to enable the development of applications that permit the easy exchange of data between any enabled computing devices. XML separates the underlying data from how the data is displayed. This schema effectively "unlocks" the data so that it can be reorganized, edited, and exchanged with any Web site, device, or enabled application.

In addition to XML, the .NET Framework utilizes other rapidly emerging standards:

Components of .NET and Product Layers

The .NET Framework consists of three primary layers. The universal run-time engine handles the lowest level of services, which includes thread management. Conceptually similar to Sun Microsystems's Java Virtual Machine, this engine manages environmental matters. A common class library rests on the universal run-time engine. The code objects can communicate with applications written in any programming language. This facility makes it possible to use large amounts of legacy code for .NET-enabled environments. Active Server Pages Plus is the highest layer and serves to separate scripts from Web-based code.

The .NET initiative was initially a vision exposed by Microsoft Chairman and Chief Software Architect Bill Gates. Unlike so many industry "visions" of the future, the concepts were soon transformed in a Framework with a wide range of Windows 2000-centric products. Products such as Microsoft Exchange 2000 and Microsoft SQL Server 2000 are the first component products to be released with .NET-enabling technology. As the following list shows, the complete suite of .NET products provides an impressive solution set. In addition to server back-end products, flagship customer products like Microsoft Office are emerging as .NET-enabled.

BACK-END APPLICATIONS AND TOOLS

MID-TIER SUITES

FRONT-END TIER

The development of applications that take full advantage of .NET is critical to its ultimate success. Microsoft released Visual Studio.NET in early 2002.

The release of new versions of .NET Servers together with completely new products is anticipated to continue at fever pace. Don't be surprised if the names of the products just mentioned undergo change. As more .NET components are added, the ability of these products to take full advantage of underlying Windows Server 2003 functionality should be enhanced.

NOTE

At the time of this book's publication, Microsoft was making considerable noise about .NET My Services (formerly code named "hailstorm"). This is a rapidly evolving technology that should be commercially available soon.

.NET My Services is a family of user-centric Web services. The purpose of the technology is to enable businesses to build deeper customer relationships and improve operational efficiency. Another stated objective is to make applications and devices easier for consumers to use. One portion of the technology is .NET Alerts, which includes communication tools that permit direct interaction between businesses and clients.

Use of .NET My Services is activated and controlled by the user optionally. For example, a .NET Alerts provider can send an XML message to the .NET Alerts service. The service routes the message to a user's desktop, cellular phone, mobile device, or e-mail address. The user determines where the message is delivered. As an administrator, you should keep an eye on how this technology evolves.


BackOffice Suite Moves Forward as Renamed .NET Products

The much ballyhooed BackOffice suite that supplemented Windows NT and Windows 2000 has quietly slipped to the very back of the office. Although the Back Office bundle is no longer marketed, the individual components are available. Several of these products have been renamed, as have other server products, including:

Microsoft Operations Manager

Microsoft provides three options in server products designed to assist administrators: (1) Application Center, (2) System Management Server (SMS), and (3) the new Microsoft Operations Manager (MOM). We provide an overview of these three optional administrative server products in Chapter 17; here we offer an overview of MOM to underscore the potential importance of this tool set for administration. Stated simply, MOM extends the management tool set of Microsoft operating system servers and .NET Enterprise Server products. Through third-party extensions from vendors like NetIQ, other platforms can also be consistently managed. The following are some major features of MOM:


  Previous section   Next section
Top