1. Creating Manageable Setups With The Windows® Installer (Part 2 of 2) Rob Collie, Program Manager Windows Installer Microsoft Corporation Jim Masson, Program Manager Windows NT Administration Microsoft Corporation

2. Our Mission Create a package for Cosmo Define the product
Sample application from inside OLE
Define the product
Define the features
Define the components
Demo working install

3. A Word About Tools The concepts in this talk are tool independent
Contact your favorite setup toolkit vendors
“Rainier” release of Visual Studio®
We will be illustrating those concepts using the InstallShield for Windows Installer tool

4. Features, Components, Resources, And Entry Points
Product
(Office)
Feature 2
(Excel)
Feature 1
(Word)
Feature 3
(Word Speller)
Feature 4
(Excel Speller)
Component 1
(WordCore)
Component 3
(ExcelCore)
Component 2
(MS Speller)
Resource
(Registry Key)
(winword.exe)
(excel.exe)
(Mssp.dll)
Entry Point
(.doc)
(Shortcut)
(.xls)
(CLSID)

5. Defining The Product The largest installable unit
Corresponds to a single .MSI file
Has a single product code GUID
Steps to define product:
Decide what should be deployed as a unit
Create a new .MSI file
Give the product a friendly name
Give the product a product code

6. Product Defined
Product
(Cosmo)

7. Defining Features Smallest unit of a product to the user
Can also be installed from the API
Must install a feature to get anything
Steps to define features:
Lay out the feature tree
Name and describe the features
Map dependencies in the tree
Decide what choices to give the user
Decide what choices to give the API
The demo for this slide will be to actually populate the Feature table in the tool.

8. Product And Features Defined
(Cosmo)
Feature
(CosmoExe)
(DataTran)

9. Defining Components Atomic Refcounted as a unit
Installed and removed as a unit
Refcounted as a unit
Allows non-file refcounting
Key file and “supporting cast”
Resources and entry points not shared across components
Smallest unit of sharing across products/features
Component Code GUID identifies narrow functionality
The fifth bullet is the point where we can spin small components to the developer’s advantage - it came back to me tonight.

10. Defining Components Steps to define components:
Start with your file list
Identify “entry point” files
Most binary files fall into this bucket
Create one component for each
Set the entry point file as the keypath
Gather up the supporting resources
Break up by install directory
Need another term for "entry point"
I think the "demo" portion of this slide is a partitioning exercise _Outside_ of the tool.

11. Defining Components Things to avoid:
Two files in one component that ship separately
E.g., a file my company produces and a file some other company produces
Move away from self registering files
COM+
Use provided tables instead
Registry, Class, ProgId, etc… tables
Don't know what to do here. Any ideas?

12. Product, Features, Components
(Cosmo)
Feature
(CosmoExe)
Component
(CosmoExe)
(DataTranDll)
(InOleDll)
Feature
(DataTran)

13. Populating Components
Resources
Files
Registry entries
Entry points
Shortcut
CLSID
Extension server
Once we're done partitioning, it's time to dive into the tool and populate all of the resource tables. We'll spend a lot of time on this slide.

14. Completed Product Diagram
(Cosmo)
Feature
(CosmoExe)
Feature
(DataTran)
Component
(CosmoExe)
(DataTranDll)
(InOleDll)
Resource
(Registry
Data)
(cosmo.exe)
(datatran.dll)
(inole.dll)
Entry Point
(.csm)
(Shortcut)
(ProgId)
(CLSID)

15. Putting It All Together
Assign and publish
Install on demand
Resiliency
Transacted install
Uninstall
Demo the nifty features of the biggest and baddest installer to ever walk the planet. Look how easy that was.

16. Next Steps Start using it!
Obtain a tool from your favorite setup toolkit vendor
Get the SDK on the conference DVD
Windows 95, Windows 98, and Windows NT® 4.0
Try packaging your latest shipping version
Plan on fully leveraging the Windows Installer in your next version
Learn about the API
Next Session: MGMT 005

17. Call To Action Empower your applications to be managed!
Separate user and machine data
See MGMT 001
Policy enable your application
See MGMT 001, MGMT 006
Create a Windows Installer package
See MGMT 003, MGMT 004
Leverage the Windows Installer API
See MGMT 005
Leverage Active Directory for Application Data
See DS 05, DS 06

18. Windows NT 5.0 Logo Leverage your investment in Windows Installer
Install/uninstall is top concern among customers
1 of 4 key areas of the new Windows NT 5.0 logo
Follow up info
Draft requirements:
On the conference DVD
Feedback: by 11/15

19. Questions And Answers