Defy Occassionally Connected Challenges With Smart Client Applications

Clint Edmonson Architect Evangelist Microsoft Corporation www.notsotrivial.net

WEB 2.0 ASP.NET AJAX WinForms WPF Silverlight ClickOnce XBAP InfoPath MOSS

Support Manage Sell Manufacture Specify “ Finished” Services

Microsoft Dynamics™ CRM Live

Live Meeting Service

Hosted Exchange, SharePoint®, Office Communication Server

“ Attached” Services

Exchange Hosted Services (Forefront, filtering)

Windows Update

Windows OneCare

“ Building Block” Services

Virtual Earth™

BizTalk Services® (relay, authentication)

Live ID and online services

Software Developers Today Are Expected To Maximize The Web Even when it is not available

Line of business

Field force application

Point of sale

Branch office

Home Entertainment

Media Center/TIVO

Media players

Home Appliances

Leverage both the local and remote resources Enabling user productivity anytime, anyplace, regardless of network reliability Enabling data to move freely between various endpoints with varying types of data in a collaborative model

Optimize Online,

Enable Offline

for:

I need an application that works when I am not connected

Challenge

Visual Studio 2008 provides a local database cache wizard that provides turn-key offline capabilities for your application

Solution

Offloads detailed questions to the client

Enables local processing, closer to the user

Enables offline scenarios

Microsoft Sync Framework

Common Sync Metadata and Runtime “ Make-it-simple” Services Protocol and Store Providers 3 rd Party Providers OCS Framework API “ Better-together” Applications Knowledge Versions Change Enumeration Conflict Detection Metadata Store Anchor Providers “ Simple” Providers RSS/ATOM File Provider Relational Provider SQL Change Tracking Sync for ADO.NET 1 st Party API Astoria Provider 3 rd Party API

SyncAgent SyncTable SQL Server Compact 3.5 Client SyncProvider SyncGroup Server DB

SyncAgent Overall Orchestration

ClientSyncProvider Local Store Implementation

ServerSyncProvider Aggregates SyncAdapters

SyncTables Clients interest in what the server has to offer

SyncGroup Transaction Boundary for SyncTables

Server Schema Changes Saves as scripts for later execution

SyncAdapter Server SyncProvider Data Access Data Forms

Conflicts can occur during synchronization Challenge

Enabled by extending the Sync Designer

Client and Server Providers have conflict events

Business rules must be re-run

(Not really any different than a connected system)

Solution

How do we get this to work in a distributed, services based environment? Challenge The Sync framework includes a transport layer to bridge the client and server providers together through a WCF sync adapter Solution

SyncTable SQL Server Compact 3.5 Client SyncProvider SyncGroup Server DB

Move the server components to another dll, hosted on a remote server

Shim in a service (WCF) and a matching proxy

SyncAgent Data Access Data Forms SyncAdapter ServerSyncProvider Transport Service Service Proxy

SELECT CT.ProductID, CT.SYS_CHANGE_OPERATION, CT.SYS_CHANGE_COLUMNS, CT.SYS_CHANGE_CONTEXT FROM CHANGETABLE(CHANGES SalesLT.Product,@last_synchronization_version) AS CT

VS 2005 SP1 Visual Studio 2008 SQL Server 2008

Building resilient applications is the future, not a stop gap

It’s how all important resources are managed

Design your apps to cache from the beginning

When things are connected, they work great

When “stuff” happens, your business continues to function

Install Visual Studio 2008 Trial version available http://msdn.microsoft.com/vstudio

Visit the .NET Framework Developer Center http://msdn.microsoft.com/netframework

Visit the Sync Framework Developer Center http://msdn.microsoft.com/sync

Clint Edmonson’s Blog http://www.notsotrivial.net

Simon Guest’s UX IQ http://simonguest.com

© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.