1 / 17

Configuring ClickOnce to best work for your deployment scenario   

Configuring ClickOnce to best work for your deployment scenario   . Saurabh Pant Program Manager Microsoft Corporation. ClickOnce Deployment Framework. Smart Client Deployment meets Web Deployment Run an Application by Clicking on a URL Update the Application by Updating on Server

chloe-abbott
Download Presentation

Configuring ClickOnce to best work for your deployment scenario   

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Configuring ClickOnce to best work for your deployment scenario    Saurabh Pant Program Manager Microsoft Corporation

  2. ClickOnce Deployment Framework • Smart Client Deployment meets Web Deployment • Run an Application by Clicking on a URL • Update the Application by Updating on Server • Isolated Low Impact Declarative Installation • Auto Update • Flexible Declarative Update Options • Rich Programmatic Extensibility • Deep Microsoft Visual Studio Integration • Rich Security Model • CLR CAS sandboxing • Permission elevation prompting w/ Authenticode

  3. Choosing Your Installation Technology

  4. What to Use When • Use ClickOnce… • When you are building Per User, Isolated applications targeting the .Net runtime 2.0+ • Use Windows Installer… • For all other applications the Windows Installer continues to provide the best install, management and servicing support on Windows Vista and down-level platforms

  5. Using MSI and ClickOnce Install the application using ClickOnce, the supporting impactful/shared framework using MSI • Application = Machine Impactful + Per- User = Pre-Requisites + Application Code = Infrequent Updates + Frequent Updates = MSI + ClickOnce Recommendation remains consistent in Orcas

  6. Typical Deployment Scenario

  7. Application Branding?

  8. .Net 2.0 Deployment Recommendations • App Developers deliver App bits to the Enterprise • Enterprise to ‘brand’ the Application • Authenticode signature • Product/Publisher/SupportUrl • Publish Location needs to be known while ‘branding’ • Publish Location burnt into Signed Manifest • Prevents Deployment from being hijacked • Prevents loss of Data due to install Url change

  9. .Net 2.0 Deployment Recommendations … • ISVs wanting to preserve ‘branding’ • Online Applications • ISV handles Signing (Web Service …) • Share Authenticode Key? • Enterprises wanting to avoid re-signing (XCopy Publishing) • Online Applications • ISV handles Signing Do NOT modify .application contents without updating its identity

  10. New in Orcas • Application Manifest can provide App Branding

  11. New in Orcas … • Publish Location can be excluded from .application for an Installed App

  12. Orcas Deployment Recommendations • Default recommended scenario same as .Net 2.0 • App Developers deliver App bits to the Enterprise • Enterprise to ‘brand’ the Application • Publish Location needs to be known while ‘branding’ VS to generate the same default manifests

  13. Orcas Deployment Recommendations … • ISVs wanting to preserve ‘branding’ • App Manifest contains branding Information and a tag specifying <Use Application Manifest for Trust/Branding> • Enterprise can sign the .application with any self-sign cert • ISVs do not need to share their Authenticode Certificates! • Publish Location needs to be known while signing not branding ISVs need to explicitly Opt Into the above behavior The enterprise can trump the ISVs choice by modifying the App Manifest to use enterprise branding

  14. Orcas Deployment Recommendations … • Enterprises wanting to avoid re-signing (XCopy Publishing, App Replication) • Exclude Publish Url from the .application • Caveats • Application can now potentially be hosted by Evil.com • Same application cannot be installed from two different URL • Explicitly blocked by ClickOnce to prevent data loss

  15. Also New in Orcas … • Xbrowser Support • ClickOnce will work with Non IE Browsers Out of the Box • Requires the .application to contain the Publish Url • OOB no support for Query Strings • Public API exposed to facilitate developing a Xbrowser plugin for ClickOnce FireFox Demo

  16. Resources • WindowsForms.Net Deployment Page [http://www.windowsforms.net/features/deployment.aspx] • Saurabh's Blog [http://blogs.msdn.com/saurabh] • Orcas Oct CTP

  17. Live from Redmond … • 14-Nov [Steve Lasker] • Live From Redmond: Smart Client: Offline Data Synchronization and Caching for Smart Clients • link • 28-Nov [Saurabh Pant] • Live From Redmond: Client Application Services in Orcas • link • 4-Dec [Steve Lasker] • Live From Redmond: Visual Studio: Developing Local and Mobile Data Solutions with SQL Server Everywhere • link • Dec 6 [Mahesh Prakriya] • Live From Redmond: IronPython: Developing agile but rich client applications using Python • link

More Related