Description of the Application Architecture for .NET: Designing Applications and Services guide (829029)



The information in this article applies to:

  • Microsoft .NET Framework 2.0
  • Microsoft .NET Framework 1.1
  • Microsoft .NET Framework 1.0
  • Microsoft Visual Studio 2005 Standard Edition
  • Microsoft Visual Studio 2005 Professional Edition
  • Microsoft Visual Studio .NET (2003), Enterprise Architect Edition
  • Microsoft Visual Studio .NET (2003), Enterprise Developer Edition
  • Microsoft Visual Studio .NET (2003), Academic Edition
  • Microsoft Visual Studio .NET (2002), Professional Edition
  • Microsoft Visual Studio .NET (2002), Enterprise Architect Edition
  • Microsoft Visual Studio .NET (2002), Enterprise Developer Edition
  • Microsoft Visual Studio .NET (2002), Academic Edition
  • Microsoft SQL Server 2000 (all editions)
  • the operating system: Microsoft Windows 2000

SUMMARY

This article discusses the Microsoft guide Application Architecture for .NET: Designing Applications and Services. This guide contains design-level guidance for the architecture and the design of Microsoft .NET Framework-based applications and services that are built on Microsoft Windows 2000 and the .NET Framework 1.0. This guide focuses on partitioning application functionality into components. The chapters in this guide discuss the key design characteristics of components. They also explain how security, management, and communication apply to each layer. This guide also explains how to deploy the components.

MORE INFORMATION

The Application Architecture for .NET: Designing Applications and Services guide is made up of the following five chapters:
  • Chapter 1 - Introduction
    This chapter presents the overall goal of distributed application design. It explains how services and service integration relate to conventional application development. This chapter also contains a simple retail scenario that is used for examples throughout the guide.
  • Chapter 2 - Designing the Components of an Application or Service
    This chapter discusses how a distributed application is built by starting with the user interface. It identifies different types of components or layers that are frequently used in successful applications. This chapter describes the major technology or design decisions that you must consider. This chapter also discusses a set of principles that you can use as a guide when you design these components.
  • Chapter 3 - Security, Operational Management, and Communications Policies
    This chapter discusses how different policies, such as authorization and exception management, affect the design of the application layers. It describes how design decisions in these areas can affect your whole application. This chapter also discusses how to choose the communication mechanisms that your application will use.
  • Chapter 4 - Physical Deployment and Operational Requirements
    This chapter discusses how to deploy the logical component layers that are presented in the previous chapters in an infrastructure that is built of many physical tiers. This chapter also describes common deployment patterns that occur when the logical component layers, the physical tiers, and the operational requirements are combined successfully.
  • Chapter 5 - Appendices
    The appendices include a glossary, a map of Microsoft products and technologies that you can use to implement or to enhance the application component layers that are discussed in chapter 2, and a list of related patterns and names that are applied to these layers in the computer industry.

REFERENCES

For more information about this guide, visit the following Microsoft Developer Network (MSDN) Web site:

Modification Type:MajorLast Reviewed:2/1/2006
Keywords:kbvs2005swept kbvs2005applies kbPAG kbGuidelines kbService kbDeployment kbArchitecture kbinfo KB829029 kbAudDeveloper