User Interface Process (UIP) Application Block - Version 2.0
|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.
Shop for patterns and practices books online [Content link no longer available, original URL:http://shop.microsoft.com/practices]
Naveen Yajaman, Edward Jezierski, and Mohammad Al-Sabt, Microsoft Corporation; Blaine Wastell, Ascentium Corporation; Paul Slater and Nelly Delgado, Wadeware LLC, ThoughtWorks Inc.
The patterns & practices team has decided to archive this content to allow us to streamline our latest content offerings on our main site and keep it focused on the newest, most relevant content. However, we will continue to make this content available because it is still of interest to some of our users.
We offer this content as-is, without warranty that it is still technically accurate as some of the material is undoubtedly outdated. Note that the content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
Summary: This page provides an overview of the User Interface Process Application Block, Version 2.0. This block is a reusable code component that builds on the capabilities of the Microsoft .NET Framework to help you create both Web Forms- and Windows Forms-based applications. (134 printed pages)
There are two versions of the UIP Application Block. Version 1.0 was released in June 2003 and version 2.0 was released in April 2004. The block provides you with a number of features that will help you develop user interface process components, and therefore distributed applications, more efficiently. The following features are in the first version of UIP and continue to be part of UIP version 2.
- Web session resume
- Web session transfer
- Reuse of code between application types
- Development of discrete tasks
- Storage of state in state persistence providers
The following features are new to UIP version 2:
- Expanded navigation management
- Additional state persistence providers
- Layout managers
- Enable back-button support
- Usability enhancements
Microsoft Visual Basic® .NET and Microsoft Visual C#® .NET source code is supplied for version 1.0 of the UIP Application Block, together with QuickStart sample applications in each language that you can use to test common scenarios. For version 2.0 of the UIP Application Block, only Microsoft Visual C#® .NET source code is provided. However, the QuickStarts are supplied in both Microsoft Visual Basic .NET and Microsoft Visual C# .NET languages. Version 2.0 of the UIP Application Block features significant functionality and usability enhancements over version 1.0.
Click here for more information on version 1.0 of the UIP Application Block.
This guide is written for readers in one or more of the following categories:
- Software developers
This guide describes the design and features of the UIP Application Block and demonstrates how you can use the block in your applications.
Chapter 1 introduces UIP concepts and discusses the goals and features of the UIP Application Block.
To make the most of the UIP Application Block, you need to understand its design. Chapter 2 discusses the architecture of the block.
After you understand the design of the UIP Application Block, you can start developing applications with it. Chapter 3 explains the process for building the block and modifying your application to use the block. The chapter also discusses the QuickStarts provided with the block.
After you create applications that use the UIP Application Block, you will need to deploy them. Chapter 4 discusses the special considerations for deploying these applications, including prerequisites for deployment and security threats and countermeasures.
Using the UIP Application Block in a default configuration works well in most situations. However, there are times when you may want to customize certain parts of the block to be more specific to your needs. Appendix A provides guidance on extending the functionality of the block.
This appendix will help you understand many of the concepts and terminology used in the UIP Application Block and in this guide.
The UIP Application Block is designed to help you:
- Abstract all navigation and workflow code from the user interface.
- Enable the use of the same programming model for different types of application.
- Remove all state management from the user interface.
- Persist snapshot state across processes.
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 the following advisors who provided invaluable contribution:
- Mike Two, ThoughtWorks, Inc.
- Jonathan Rasmusson, ThoughtWorks, Inc.
- Greg Layok, ThoughtWorks, Inc.
- Jean-Paul S. Boodhoo, ThoughtWorks, Inc.
- Paul Gale, ThoughtWorks, Inc.
- Thomas Tannahill, ThoughtWorks, Inc.
- Richard Hurst, ThoughtWorks, Inc.
- Wei Hong, ThoughtWorks, Inc.
- Leslie Borrell, ThoughtWorks, Inc.
- David Hill, Microsoft Corporation
- Brian Pepin, Microsoft Corporation
- Mark Bolter, Microsoft Corporation
- Shawn Burke, Microsoft Corporation
- Brenton Webster, Microsoft Corporation
- Tim Osborn, Ascentium Corporation
- Prashant Bansode (Infosys Technologies Ltd)
- Guru Sundaram (Infosys Technologies Ltd)
Thanks also to the many contributors who assisted us in the production, in particular:
- Sharon Smith Jansen, Microsoft Corporation
- Tina Burden McGrayne, Entirenet
- Susan Filkins, Entirenet
- Claudette Iebbiano, Wadeware
- Sanjeev Garg, Satyam Computer Services
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.