Building Offline Applications Using Microsoft Silverlight 3

Stephen ForteChief Strategy OfficerTelerikWUX204

Speaker.Bio.ToString();Chief Strategy Officer of TelerikCertified Scrum MasterActive in the Community:

International Conference Speaker for 12+ YearsRD, MVP and INETA Speaker Co-moderator & founder of NYC .NET Developers Group http://www.nycdotnetdev.comWrote a few books: SQL Server 2008 Developers Guide (MS Press)

MBA from the City University of New YorkPast:

CTO and co-Founder of Corzen, Inc. (TXV: WAN)CTO of Zagat Survey

Out of Browser Goals

SimplicityGive the user the right default behaviorNo additional downloads for user

Follow the web rulesUse the web deployment/update modelMost applications can live within a sandbox

Out of browserdemo

Taking an App Out of Browser

Gestures (How)Context menuApplication-provided behaviorApp runs before install

User initiates action to trigger

Application TypesAlways connectedAlways disconnectedOccasionally connected

Detaching API

Manifest (AppManifest.xaml)Name, title, descriptionOptional icons

Code APIsDetach() methodExecutionStateExecutionStateChanged event modelRunningOffline property

Detached State Flow

In-browserRunningOnlineDetachingDetached (RunningOffline=false)

Out of browserDetached (RunningOffline=true)

Application Updates

Optimized for instant onBackground downloading upon identificationNext out of browser launch uses new appEvent model when update downloaded

Network Availability

Network detection key for scenario (occasionally connected apps)Silverlight 3 new APIs for detection

IP address change eventNetwork available property

Any interface (no loopback)

Best practicesDo more than just detect IP change

Interacting with Data

Out of browser IsoStoreDefault limit increase to 25MB upon Detach()Can still prompt for quota increaseStorage is shared location for in-browser and out-of-browser – not a new IsoStore

OpenFileDialog and SaveFileDialogInteraction with full file system via user action

Out of browserdemo

Debugging Methods

ChildWindow for ExceptionsAttach to SLLauncher.exe in beta

Post-beta will launch auto attach in VSIn-browser and out of browser are two instances of the app

Differences from In-browser

Additional key mappings (F keys)No HTML DOM Access

MouseWheel XmlHttp

Currently no HTML interopAssembly Cache not available

Best Practices

Download local data Check RunningOffline for state

Don’t trigger more than one HttpWebRequest at a timeKeep your code in the XAP

Silverlight versions for youIf data model changes, require a restartShow UI for major updates

www.microsoft.com/teched

Sessions On-Demand & Community

http://microsoft.com/technet

Resources for IT Professionals

http://microsoft.com/msdn

Resources for Developers

www.microsoft.com/learningMicrosoft Certification and Training Resources

www.microsoft.com/learning

Microsoft Certification & Training Resources

Resources

© 2009 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.