Difference between revisions of "Adminstudio Notes"

From WolfTech
Jump to navigation Jump to search
m
m
Line 1: Line 1:
==Day 1==
+
==Day 1 - Ch 1-4 ==
  
 
'''Chapter 2 - Storage Structure (pg 29-30)'''
 
'''Chapter 2 - Storage Structure (pg 29-30)'''
Line 39: Line 39:
 
----
 
----
  
==Day 2==
+
==Day 2 - Ch 5==
  
 
(Snapshot) Single Step vs Multiple Step
 
(Snapshot) Single Step vs Multiple Step

Revision as of 15:15, 20 May 2008

Day 1 - Ch 1-4

Chapter 2 - Storage Structure (pg 29-30)

C:\My Storage Structure\AppName_AppVer_OS_LANG

~\1_LegacyInstallation

  • contains copy of original installation program

~\2_Documentation

  • documentation of project: request, process, notes, etc

~\3_RepackagerAndSourcefiles

  • contains files captured by Repackager

~\4_ProjectFiles

  • contains project files edited/created by Installshield Editor
  • may consider creating subfolders within for different versions of projects

~\5_CompeletedMSI

  • contains finished releases
  • again, may create additional subfolders for different releases

  • Map C:\My Storage Structure\ and C:\Program Files\Macromedia\AdminStudio\8.5\ on virtual machine

  • Add C:\Program Files\Macromedia\AdminStudio\8.5\Common to PATH of virtual machine (for repackager to work)

  • C:\AdminStudio Shared\isrepackager.ini -> Default exlusions

Chapter 4 - Repackager (pg 58)

Best Practices

  • Run repackager over the network (from a share), not locally
  • Repackage on a clean image
  • Exit all applications before repackaging
  • Best to use Installation monitoring process

Day 2 - Ch 5

(Snapshot) Single Step vs Multiple Step

  • Single Step launches setup program after pre-check, Multiple step closes after pre-check
  • With multiple step, re-run repackager after installations are complete to continue snapshot process.

Chapter 5 - InstallShield Editor (pg 97)

  • Tools -> Options
    • General tab, check "Enforce Setup Best Practices"
    • Directory tab, check "Cleanup unused directories"

  • "Change/Remove" button in Add/Remove Programs means program is legacy installation (not an .msi)

  • ProductVersion - MM.mm.bbbb (Major.minor.build)
    • example, 1.00.0100

Using properties for conditional statements (pg 129)

  • Comparing Properties and property values in order to determine whether a certain function should run
    • install or launch conditions, ex: fails if OS is not a WindowsNT type (NT, 2000, XP)
    • uses boolean lang (and, or, =, >=, etc)

VersionNT

  • 400 Windows NT
  • 500 Windows 2000
  • 501 Windows XP
  • 502 Windows Server 2003
  • 600 Windows Vista

Privileged, true if user has admin rights or if package has elevated privs
AdminUser, true only if user has admin rights


  • Release Wizard
    • Typically use network image for packages
  • Validation
    • Build -> Validation
    • Use Full MSI Validation
    • ICE33 can ignore (pretty much always happens)