Bookmark and configuration file for installation sequence

• US 20080244564A1
• Filed: 03/26/2007
• Published: 10/02/2008
• Est. Priority Date: 03/26/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Sonkin, Dmitry, Greisen, Marc, Vartak, Unmesh
• Granted Patent: US 8,239,854 B2
• Time in Patent Office: Days
• US Class Current: 717/175
• CPC Class Codes: G06F 8/61 Installation

Abstract

A bookmark file is stored in persistent storage and is updated as various tasks are completed during an installation process. The bookmark file may be read when an installation process is started so that the installation process may continue from a point after the last successfully completed task, if the installation process had failed and was restarted. The bookmark file may also include data collected from a user interface during the installation process. When an installation process is restarted, some embodiments may present the data in a user interface for the user to modify. The installation process may be defined in a configuration file that includes metadata that defines the sequence of installation tasks as well as some error handling for various tasks.

Claims

1. A system comprising:

a plurality of setup modules;

a configuration file comprising configuration data used by at least one of said plurality of setup modules;

a sequence file comprising a definition of a sequence of said setup modules to be executed;

a bookmark file in a persistent storage, said bookmark file adapted to store a last completed setup module;

a setup engine adapted to;

determine a next setup module from said sequence file and said bookmark file;

store an first entry in said bookmark file before starting said next setup module;

cause said next setup module to be executed;

detect that said next setup module has successfully completed execution; and

store a second entry in said bookmark file after said next setup module has successfully completed execution.

2. The system of claim 1 further comprising:

a plurality of user interface modules; and

a setup file comprising relationship definitions for at least one relationship between at least one of said plurality of setup modules and at least one of said plurality of user interface modules.

3. The system of claim 2, said setup engine further adapted to:

determine a related user interface module for said next setup module; and

display said related user interface module.

4. The system of claim 1, said setup modules comprising at least one from a group composed of executable files and interpreted files.

5. The system of claim 1, said sequence file further defining a dependency between a first setup module and a second setup module.

6. The system of claim 1, said sequence file further defining at least two of said setup modules that may be executed in parallel.

7. The system of claim 1, said sequence file further defining at least one error handling sequence for one of said setup modules.

8. The system of claim 7, said setup engine further adapted to:

determine that an error has occurred during execution of said next setup module; and

performing said error handling sequence.

9. The system of claim 1 further comprising a single file comprising at least one combination from a group composed of:

said configuration file and said sequence file;

said configuration file and said bookmark file;

said sequence file and said bookmark file; and

said configuration file, said sequence file, and said bookmark file.

10. The system of claim 1 further comprising:

a setup notifier adapted to detect a last of set setup modules to have been successfully completed, said setup notifier being adapted to be executed when said system is started.

11. The system of claim 1, said sequence of setup modules defining an installation process for a software component on said system.

12. The system of claim 1, said sequence of setup modules defining an installation process for a software component on a second system.

13. A method comprising:

reading a sequence file comprising a sequence of setup modules to be executed;

reading a bookmark file comprising a last completed setup module;

determining a next setup module from said sequence file and said bookmark file;

storing a first entry in said bookmark file before starting said next setup module;

causing said next setup module to be executed;

detecting that said next setup module has successfully completed execution; and

storing a second entry in said bookmark file after said next setup module has successfully completed execution.

14. The method of claim 13 further comprising:

detecting that an error has occurred during execution of said next setup module; and

performing an error handling sequence defined in said sequence file.

15. The method of claim 14 wherein said detecting than an error has occurred is performed when a system is started.

16. A computer readable medium comprising computer executable instructions adapted to perform the method of claim 13.

17. A method comprising:

detecting that a last attempted setup module was started but not completed, said detecting being performed by reading a bookmark file;

reading a sequence file comprising a definition of a plurality of setup modules to be executed;

reading a configuration file comprising configuration data used by at least one of said plurality of setup modules, said configuration data comprising last attempted module data;

reading a setup file comprising relationship definitions between at least one of said setup modules and at least one user interface module;

determining a related user interface module for said last attempted setup module; and

displaying said related user interface module with at least a portion of said last attempted module data.

18. The method of claim 17 further comprising:

determining an error handling sequence for said last attempted setup module, said error handling sequence being determined from said sequence file; and

performing said error handling sequence.

19. The method of claim 17, said detecting that a last attempted setup module being performed when a system is restarted.

20. A computer readable medium comprising computer executable instructions adapted to perform the method of claim 17.