Design and Implementation Guidelines for Web Clients
|This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies.
This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
Edward Jezierski and Naveen Yajaman, Microsoft Corporation; Andy Olsen, Content Master; Diego Gonzalez, Pablo Cibraro, and Daniel Cazzulino, Lagash Systems SA
Microsoft .NET Framework
This page provides an overview of Design and Implementation Guidelines for Web Clients. This guide provides advice on how best to implement logic in the presentation layer of a distributed application. This guide is designed to accompany the User Interface Process Application Block; this application block provides a template implementation for user interface process components.
This guide is written for readers in one or both of the following categories:
- Software developers
This guide addresses specific goals of presentation layer component design. This guide provides prescriptive recommendations and code samples that enable you to use design patterns and Microsoft .NET Framework programming idioms effectively in the presentation layer of your applications. The intent of this guide is to help you increase the portability, maintainability, scalability, security, and overall design quality of your presentation layer code; it does not discuss aesthetic user interface design issues.
This chapter introduces the topics in this guide and provides guidance on basic terminology. It also notes the decisions the authors of this guide assume you have already made.
This chapter describes how to separate the responsibilities of components in the presentation layers by using common design patterns.
This chapter describes how to make ASP.NET code easier to implement and maintain.
This chapter describes the correct way for components in the user interface (UI) to access, present, update, and validate data input, and how the UI participates in maintaining data integrity.
This chapter describes the types of state used in the presentation layer and offers guidance about how to manage state in applications written for the Web.
This chapter describes how to increase performance and responsiveness of the code in the presentation layer by using multithreading and asynchronous programming.
This chapter describes how globalization and localization requirements affect the development of your presentation layers.
Appendix A describes how security and manageability considerations affect the design of presentation layer components.
This appendix provides code samples to illustrate the various techniques described throughout this guide.
Design and Implementation Guidelines for Web Clients is designed to provide advice on how best to implement logic in the presentation layer of a distributed application. The example code is provided as source code that you can use "as is" or customize for your application. Support is available through Microsoft Product Support for a fee.
Many thanks to Brenton Webster, .NET Enterprise Architecture Team, who provided invaluable assistance.
Thanks also to the many contributors who assisted us in the production, in particular:
- Edward Lafferty, patterns & practices
- Sharon Smith, patterns & practices
- Andrew Mason, patterns & practices
- Hemang Naik, Prashant Bansode, Shishir Jhaveri, and Sameer Tarey, Infosys Technologies Limited
- Tina Burden, Entirenet
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.