IntroducingClickOnceTheNewApplicationDeployment.ppt

Introducing ClickOnce: The New Application Deployment Model forWindows Forms and “Avalon” Jamie Cool (jamiec@) Program Manager Microsoft Corporation Agenda Client Deployment Re-visited ClickOnce Walkthrough Demos Reliable easy web based installs Deployment update options Security model Questions Deployment Problems Installing client apps is fragile Will the install of app1 break app2? Traditional DLL hell problem Installing client apps is hard expensive Must touch every client Both for 1st time install subsequent updates ClickOnce Vision Bring the ease reliability of web application deployment to client applications. ClickOnce User Experience Running a client app from the web V1 of the .NET Framework Addressed #1 app safety issue, DLL Hell Application Isolation Controlled versioning of shared components Did not address application install safety Began to address ease of deployment Run from URL/UNC exes, browser controls… ClickOnce builds upon these technologies Development Experience Integrated VS Support Integrated to core project system Setup is not a post-development operation Publish Wizard Copies application to web server FTP, UNC, FrontPage Server Extensions ClickOnce End-To-End Building, deploying updating a client application The Best of the Client Web Install Goals Reduce install fragility Allow what’s low impact Ex. App file copy, start menu integration, etc… Can always undo what was installed Disallow what’s not low impact Apps never run with admin rights (LUA) Driver registration, COM objects, etc.. Custom actions; large source of install uncertainty Expand the definition of “low impact” Requires OS Changes. Starts with Longhorn Install-Time Support VS BootstrapperBridging the Gap to the Future Lay down application pre-reqs Ex. (.NET FX, Crystal, DirectX, MDAC, etc…) Must be an admin to run Bootstrapper Extensible Install ClickOnce application after pre-reqs Use ClickOnce for auto-updates No auto-updates of pre-reqs components