Microsoft Technology Licensing, LLC

William L Cheng

Erik Fortune

Jason Ghssane Salameh

Andres Carlo Petralli

Phillip E Smith

Adam D Stritzel

Carolyn L Napier

Hemchander Venkateshwara Sannidhanam

Robert Charles Flaming

Venkata Kiran Kumar Annamraju

Kin Yip Kenneth Wong

Phillip Smith

Jonathan L Davis

Ravi Kiran Kunapuli

Kyle Grayson Conroy

For applications that are designed to operate across multiple computer environments, an application distribution service may store multiple different versions of application packages, the different versions being applicable to different computing environments. Application targeted metadata associated with the application packages may be utilized to quickly diagnose the applicability of the application packages to a client device with low bandwidth cost, and before any package distribution is commenced.

Deployment meta-data based applicability targetting

Registration of an application in a per-user registration model includes the creation and storage of duplicate registration data for multiple user accounts present on a system. This duplication of registration data may be reduced by storing at least a portion of identical data in a per-machine location in the system memory where it is accessible to all user accounts. Instead of needing to separately re-compute and/or re-store duplicate registration data in multiple per-user locations in the memory, each user account may access and utilize the registration data stored in the per-machine location. Pre-computing and storing a portion of the application registration data in a per-machine location in the memory may also allow the system to defer the registration of the application.

De-duplication of per-user registration data

Described is installing multiple software packages to a computing device in a single transaction, whereby the multiple package installation commits if successful, or the device is rolled back to a determined state if unsuccessful. A client process provides a system service (installer) with a package, and the service partitions package installation actions into execution, commit and rollback phases, with the execution phase run for each package. If successful, the transaction is committed by performing the multiple commit phases. If unsuccessful, the installation is rolled back via the rollback phases. The phases may be interleaved, with execution and commit phases performed in FIFO order, and rollback phases performed in LIFO order. A client process may dynamically determine which packages to install, a client process may be embedded in a package and join the transaction, and/or one client process may delegate control to another client to add package actions to the transaction.

Transactional multi-package installation

Growing community of inventors

Redmond, WA, United States of America

William L Cheng