Dynamically identifying dependent files of an application program or an operating system

• US 20050091192A1
• Filed: 10/12/2004
• Published: 04/28/2005
• Est. Priority Date: 10/24/2003
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Li, Eric, Rector, John Austin, Probert, David B.
• Application Number:
  US10/963,479
• Publication Number:
  US 20050091192A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 21/6281 at program execution time, where the protection is within the operating system
• CPC Class Codes: G06F 2221/2145 Inheriting rights or properties, e.g., propagation of permissions or restrictions within a hierarchy
• CPC Class Codes: G06F 8/62 Uninstallation

Abstract

Tracking creation of one or more files by an application program or operating system. A method of the invention dynamically maintains a list of files or other resources associated with a particular application program or operating system. The method maintains the list by detecting creation of a file, determining an identity for the file, identifying a list associated with the file identity, and adding the file to the list.

Claims

1. A method for tracking creation of one or more files associated with an application program, said method comprising:

detecting creation of a file by an application program;

determining an identity for the detected file;

identifying a list associated with the determined identity, said list representing a collection of files associated with the application program; and

adding the detected file to the identified list.

2. The method of claim 1, wherein detecting creation of the file by the application program comprises detecting creation of the file by the application program during execution of the application program.

3. The method of claim 1, wherein detecting creation of the file by the application program comprises detecting creation of the file by the application program during installation of the application program.

4. The method of claim 1, wherein detecting creation of the file by the application program comprises detecting creation of a user file by the application program responsive to a request from a user.

5. The method of claim 1, further comprising distinguishing between creation of a user file and creation of an application file.

6. The method of claim 1, further comprising analyzing metadata to determine whether the file is user-specific or application-specific.

7. The method of claim 1, wherein detecting creation of the file by the application program comprises detecting creation of a name in a system namespace.

8. The method of claim 7, wherein detecting creation of the name in the system namespace comprises detecting creation of a directory in a file system.

9. The method of claim 1, wherein one or more computer-readable media have computer-executable instructions for performing the method recited in claim 1.

10. One or more computer-readable media having computer-executable components for tracking creation of one or more files associated with an application program, said components comprising:

a filter component for detecting creation of a file by an application program;

an identity component for determining an identity for the detected file;

a list component for identifying a list associated with the determined identity, said list representing a collection of files associated with the application program; and

a maintenance component for adding the detected file to the identified list.

11. The computer-readable media of claim 10, wherein the filter component detects creation of the file by the application program during execution of the application program.

12. The computer-readable media of claim 10, wherein the filter component detects creation of the file by the application program during installation of the application program.

13. The computer-readable media of claim 10, wherein the filter component detects creation of a user file by the application program responsive to a request from a user.

14. The computer-readable media of claim 10, wherein the filter component distinguishes between creation of a user file and creation of an application file.

15. A method for tracking creation of one or more resources associated with an operating system, said method comprising:

determining an identity for an operating system;

detecting creation of a resource by the operating system during installation of the operating system;

identifying a list associated with the determined identity, said list representing a collection of resources associated with the operating system; and

adding the detected resource to the identified list.

16. The method of claim 15, wherein detecting creation of the resource comprises detecting creation of the resource by the operating system during an update to the operating system.

17. The method of claim 15, further comprising determining an identity for the detected resource.

18. The method of claim 15, wherein detecting creation of the resource by the operating system during installation of the operating system comprises detecting creation of a file by the operating system.

19. The method of claim 15, wherein detecting creation of the resource by the operating system during installation of the operating system comprises detecting creation of a system setting by the operating system.

20. The method of claim 15, wherein one or more computer-readable media have computer-executable instructions for performing the method recited in claim 15.

21. A system for tracking resource usage comprising:

a memory area for storing one or more resource lists, each of the one or more resource lists representing a collection of resources; and

a processor configured to execute computer-executable instructions for;

detecting creation of a resource;

determining an identity for the detected resource;

identifying a resource list associated with the determined identity from the one or more resource lists stored in the memory area; and

adding the detected resource to the identified resource list.

22. The system of claim 21, wherein the memory area further comprises one or more runtime object lists, each of said runtime object lists being associated with an executable object, and wherein the processor is further configured to execute computer-executable instructions for:

detecting creation of another runtime object;

determining an identity for the created runtime object;

identifying a runtime object list associated with the determined identity from the one or more runtime object lists stored in the memory area; and

adding the detected runtime object to the identified runtime object list.

23. The system of claim 22, wherein each of the runtime object lists stored in the memory area comprises a list of one or more of the following:

a process, a thread, a fiber, a work item, an application program, and an operating system.

24. The system of claim 22, wherein each of the runtime object lists stored in the memory area is associated with an executable object.

25. The system of claim 22, wherein the executable object comprises one or more of the following:

an application program, a process, a thread, a fiber, a work item, and an operating system.

26. The system of claim 21, wherein each of the resource lists stored in the memory area comprises one or more of the following:

a named object, an application programming interface, a file, a folder, and a system setting.

27. The system of claim 21, wherein each of the resource lists stored in the memory area comprise one or more of the following:

a registry key and a registry value.

28. A computer-readable medium having stored thereon a data structure for managing access by a collection of objects to one or more resources, said data structure comprising:

a dynamic list of runtime objects, each of said runtime objects having a common property; and

a set of privileges defining access by the runtime objects to at least one resource.

29. The computer-readable medium of claim 28, wherein the set of privileges comprises a set of one or more of the following:

rules, properties, attributes, authorized actions, and unauthorized actions.

30. The computer-readable medium of claim 28, wherein the set of privileges is stored on each of the runtime objects.

31. The computer-readable medium of claim 28, wherein the set of privileges is stored in a manifest associated with an application program.

32. The computer-readable medium of claim 28, wherein the set of privileges is stored in an extensible markup language manifest associated with an application program.