Advanced Staging Custom Rollouts

1
AdvancedStaging Custom Rollouts
2
AdvancedStaging Custom Rollouts

• To publish a test version, you must change
• Publication Versions
• Publication URL
• Installation URL (if changed)
• Updates URL (if changed)

3
AdvancedStaging Custom Rollouts

• FROG
• then www.ssw.com.au

4
AdvancedStaging Custom Rollouts

• Other Options
• Option 2
• Use the System.Deployment APIs, you could build
  your own custom logic for determining when an
  application should update use the APIs to
  instruct ClickOnce to do an update at the
  appropriate time.
• Option 3
• Have server side logic that dynamically decides
  which version of an application a user should
  have returns an appropriate deployment manifest
  for that user.

5
AdvancedAdding Custom Prerequisites
6
AdvancedAdding Custom Prerequisites
SharePoint 2007 (Beta2) hopelessly shows this
message for its prerequisite Windows Workflow
Foundation Beta 2

• We need to do better!

7
AdvancedAdding Custom Prerequisites

• To create your own package, you must have/create
• 1. redistributable component in the form of an
  EXE or MSI file
• 2. Product manifest, product.xml
• 3. Package manifest(s), package.xml
• All prerequisite packages are stored inProgram
  Files\Microsoft Visual Studio 8\sdk\v2.0\BootStrap
  per\Packages\
• Typical Directory Structure
• Reference http//blogs.msdn.com/harsh/archive/2006
  /05/31/611133.aspx

8
AdvancedAdding Custom Prerequisites Product.xml

• Sample
• ltProductxmlns"http//schemas.microsoft.com/devel
  oper/2004/01/bootstrapperProductCode"SSW.NewPrer
  equisite.1.0"gt
• ltRelatedProductsgt
• ltDependsOnProduct Code"Microsoft.Net.Fram
  ework.2.0" /gt
• lt/RelatedProductsgt
• ltPackageFilesgt
• ltPackageFile NameSSWNewPrerequisiteChk.e
  xe"/gt
• lt/PackageFilesgt
• ltInstallChecksgt
• ltExternalCheck Property"SSWNewPrerequisit
  eInstalled" PackageFile"SSWNewPrerequisiteChk.exe
  "/gt
• lt/InstallChecksgt
• lt/Productgt

9
AdvancedAdding Custom Prerequisites Product.xml

• ltProductgt
• ltRelatedProductsgt Lists products that depend
  upon or are included in the
  current product
• ltDependsOnProductgt Dependant products not
  included
• ltIncludesProductgt Dependant products included
  in this package
• ltPackageFilesgt
• ltPackageFilegt A file in the package. Specifies
  Name, Path, Remote location and public key
• ltInstallChecksgt
• ltAssemblyCheckgt Checks that an assembly exists
  in GAC
• ltExternalCheckgt Executes external program and
  check exit code
• ltFileCheckgt Checks file exists, and returns
  version number
• ltMsiProductCheckgt Check msi installation is
  complete
• ltRegistryCheckgt Check registry key value
• ltRegistryFileCheckgt check file version in
  registry

10
AdvancedAdding Custom Prerequisites Package.xml

• ltPackagegt
• ltPackageFilesgt
• ltPackageFilegt A file in the package. Specifies
  Name, Path, Remote location and public key
• ltCommandsgt
• ltCommandgt Run/install a package.
• ltInstallConditionsgt Conditions for
  bypassing, installing and failing
• ltBypassIfgt
• ltInstallIfgt
• ltFailIfgt
• ltExitCodesgt Logic for response to exit
  codes
• ltStringsgt String array containing all possible
  string messages
• ltStringgt
• ltSchedulesgt
• ltSchedulegt Defines when certain commands are to
  run
• ltBuildListgt Execute immediately after
  bootstrapper starts
• ltBeforePackagegt Execute before the
  specified package is installed

11
(No Transcript)
12
AdvancedLocalization

• There are 3 ways to approach this
• Generate one deployment for each culture, with a
  single satellite assembly included in each.
• Drawback You must be careful to publish to a
  different Web server directory or file share
  directory each time
• Include all satellite assemblies in a single
  deployment.
• Benefit creates a single deployment
• Drawback Downloads all assemblies
• Download satellite assemblies on demand.
• Drawback must be online

But, what is a satellite Assembly? Its an An
assembly containing localized resources for
another assembly