Smart Client Offline Application Block
|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, Brenton Webster, David Hill, Mohammad Al-Sabt (Microsoft Corporation); Brian Button (Murphy and Associates); Prashant Bansode, Guru Sundaram (Infosys Technologies Ltd); Bharat Rawal (Volt); Blaine Wastell (Ascentium Corporation); Roberta Leibovitz (Modeled Computation LLC)
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.
This page provides an overview of the Offline Application Block, which is intended to serve as an architectural model for developers who want to add offline capabilities to their smart client applications. The block demonstrates how to:
- Detect the presence or absence of network connectivity.
- Cache the required data so that the application can continue to function even when the network connection is not available.
- Synchronize the client application state and/or data with the server when the network connection becomes available.
This guide is written for:
- Software developers
- Application architects
This guide describes the design and features of the Offline Application Block and demonstrates how you can use the block to add offline capabilities to your smart client applications.
Chapter 1 introduces the Offline Application Block and gives a high-level description of its architecture. It also includes a customer scenario, which is further developed in Chapter 2.
Chapter 2 examines the Offline Application Block features, architecture, and design, as well as its relationship to other components that support it, such as the Caching Application Block.
After you understand the features of the Offline Application Block, you can start developing with it. Chapter 3 details the process for building the block and modifying your application to use it. The chapter also discusses the QuickStarts that are included to help you understand the steps that are needed to implement your own offline solution.
After you create your applications, you must configure, secure, and deploy them. Chapter 4 presents the steps for using the application configuration file and deploying the applications. It also discusses possible security threats and the countermeasures you can take against them.
The appendix documents the test cases used to verify that the Offline Application Block works correctly.
The ReadMe.txt file is a separate document that contains troubleshooting hints and information about known issues. To access it, click Start, click All Programs, click Microsoft Application Blocks for .NET, click Offline, and then click ReadMe.
The Offline Application Block comes with an insurance claims processing sample that offers some insight into development decisions explained in Chapter 2, "Design of the Offline Application Block." The complete code and the associated documentation for the sample are available on the GotDotNet community in the patterns & practices Smart Client workspace:
The Offline Application Block is designed to help you add offline capabilities to your smart client applications. The sample code is intended to serve as an architectural model that you can use as guidance when developing your own solutions. 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 assistance:
- Maarten Mullender, Microsoft Corporation
- Mark Bolter, Microsoft Corporation
- Scott Densmore, Microsoft Corporation
- Tim Osborn, Ascentium Corporation
Thanks also to the many contributors who assisted us in the creation and production:
- Carlos Farre, Solutions IQ
- Matthew Evans, Microsoft
- Sharon Smith, Microsoft
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.