1. Chris Jackson Architect, Microsoft @appcompatguy

3. Installer package and files File system Registry Applications Shell and app MGMT client Active directory Windows Installer API Windows Installer service  Configuration data Tracks state of installed apps and components Tracks state of installed apps and components  Install service built into OS Service on Windows NT Service on Windows NT Performs all install operations Performs all install operations  API Install and configure packages and features Install and configure packages and features Query machine state Query machine state Build packages Build packages  Package Describes required state Describes required state Configdata

5. Cognitive Stage Intellectualizing Developing Strategies Associative Stage Concentrating less Increasing efficiency Autonomous Stage Losing conscious control of what you are doing “Autopilot”

30. Purpose: Installation and distribution of developer libraries and SDKs User base: Developers (Not for use by end-users, IT Pro, etc.) Features: Excellent integration into development tools (Visual Studio/WebMatrix) **FIXME Low Security considerations (limited/no use of digital signatures) Recent cooperation between the CoApp, Visual Studio and NuGet teams is bringing native library & ExtensionSDK support-- cements NuGet as the ‘one way’ to acquire, publish and install libraries and SDKs for Windows (commercial and open source alike)

31. Purpose: Provides tools & infrastructure to build better open source on Windows Provides a common repository for publishing open source applications, libraries and languages User base: Developers, Software Publishers – tools End-users, Consumers, IT Pros—published packaged software Features: Full package management experience for Windows Packages provide frictionless installation and update of dependencies Build automation & packaging for supported open source projects Next Generation: Provide a unified interface to all Installation/Packaging software on Windows & Azure Move to next generation WiX installation engine for publishing packages

32. Purpose: Provides tools for foundational support of Windows Installer technology – create standalone MSI installers User base: Developers/Software Publishers (Not for use by end-users, IT Pro, etc.) Features: Currently supports generation of MSI-based installers Used externally by hundreds-of-thousands of publishers/developers Used internally by Office, Visual Studio and the majority of Microsoft product teams producing installers Next Generation: Support creation of alternative package types (via Simplified WiX) A new, modern installation engine (“Heavy Water”)

33. Global/OS Scope -Installs into system locations (ie, Program Files) -Full Access to Registry -May modify Environment Variables -Requires Administrator permissions User/Restricted Scope -Installation to user-specific or user-restricted locations (ie %LocalAppData%, or InetPub) -Registry Access limited to User Hive Local Scope -Most limited scope -Modifications limited to a single directory (including dependencies) -No Registry Access -Supported by “Xcopy” and “Portable” installation models -No special permissions required Online (Live) OS -Installs packages to the current OS -Traditional model (supported by everything) Offline OS -Installs apps into VM Images, or other non-live systems -Must be able to manipulate offline registry hives* (GAC, SXS) -Unsupported directly by older technologies (ie, MSI, Custom Installers)

35. http://msdn.microsoft.com/en-au/ http://www.microsoftvirtualacademy.com/ http://channel9.msdn.com/Events/TechEd/Australia/2013 http://technet.microsoft.com/en-au/