Persisting and resolving application assembly binds

• US 20060037011A1
• Filed: 10/14/2005
• Published: 02/16/2006
• Est. Priority Date: 12/05/2001
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Parthasarathy, Srivatsan, Shi, Alan
• Granted Patent: US 7,703,083 B2
• Time in Patent Office: Days
• US Class Current: 717/164
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: G06F 9/44536 Selecting among different versions

Abstract

A system and method are presented that persist assembly bind information for applications at each stage of execution of the assembly policy. New assembly bind history files are created and persisted to disc when changes in assembly bind policy results in a change in the assemblies with which the application binds. This persisted information is used to reconfigure assembly binds to a prior state when operation of the application conformed to a user'"'"'s desires. Since this assembly bind reconfiguration is on a per application basis, only the binding of the selected application is affected. Likewise, the assembly bind history files are associated with a particular user to allow personalized execution of applications on a system.

Claims

1. A computer-implemented method of persisting assembly bind information for an application executed on a computer, comprising:

recording assembly bind request information referenced in the application being executed;

recording assembly redirect information, said redirect information being determined based on an associated assembly binding policy;

determining if the assembly bind request information and the assembly redirect information should be persisted in an assembly bind history file for each application being executed; and

persisting the assembly bind request information and the assembly redirect information in the assembly bind history file when the determining is affirmative.

29. The computer-implemented method of claim 1, wherein recording assembly redirect information comprises recording assembly redirect information for each bind redirection at each level of bind policy redirection.

30. The computer-implemented method of claim 1, wherein recording assembly redirect information comprises recording assembly redirect information for all assemblies for which the application requests binds.

31. The computer-implemented method of claim 1, wherein determining if the assembly bind request information and the assembly redirect information should be persisted comprises determining if the bind history file is currently being persisted for the application based on a prior assembly bind.

32. The computer-implemented method of claim 31, wherein determining if the assembly bind request information and the assembly redirect information should be persisted further comprises determining that no previous bind history file exists, and wherein persisting comprises storing the assembly bind request information and the assembly redirect information in an in-memory data structure until application shutdown.

33. The computer-implemented method of claim 32, further comprising determining that additional assembly bind request information and assembly redirect information for another assembly bind by the application is stored in memory, and persisting the additional assembly bind request information and assembly redirect information for the another assembly bind in the assembly bind history file.

34. The computer-implemented method of claim 31, wherein determining if the assembly bind request information and the assembly redirect information should be persisted further comprises determining that a previous bind history file exists, and further comprising determining that no difference exists between the previous bind history file and the assembly bind request information and the assembly redirect information, and wherein persisting comprises storing the assembly bind request information and the assembly redirect information in an in-memory data structure.

35. The computer-implemented method of claim 31, wherein determining if the assembly bind request information and the assembly redirect information should be persisted further comprises:

determining that a previous bind history file exists,

determining that a difference exists between the previous bind history file and the assembly bind request information and the assembly redirect information,

determining that additional assembly bind request information and assembly redirect information for another assembly bind by the application is stored in memory, and

persisting the additional assembly bind request information and assembly redirect information for the another assembly bind in the assembly bind history file.

36. The computer-implemented method of claim 1, wherein persisting the assembly bind request information and the assembly redirect information in the assembly bind history file comprises recording temporal information for the assembly bind.

37. The computer-implemented method of claim 36, further comprising indexing the assembly bind history file by the temporal information.

38. The computer-implemented method of claim 1, wherein persisting the assembly bind request information and the assembly redirect information in the assembly bind history file comprises associating the assembly bind history file with user information.

39. The computer-implemented method of claim 38, wherein associating the assembly bind history with user information comprises storing the assembly bind history file in a non-roaming user-profile directory.

40. The computer-implemented method of claim 1, further comprising retrieving the assembly bind history file, and binding all assemblies for the application in accordance with the assembly bind history file.

41. The computer-implemented method of claim 40, wherein a plurality of assembly bind history files are persisted, and wherein retrieving the assembly bind history file comprises retrieving all of the plurality of assembly bind history files, further comprising receiving a user selection of one of the plurality of assembly bind history files, and wherein binding comprises binding all assemblies for the application in accordance with the one of the plurality of assembly bind history files.

42. The computer-implemented method of claim 1, wherein recording assembly bind request information comprises recording a predetermined set of one or more assembly binds for the application.

43. The computer-implemented method of claim 1, wherein persisting the assembly bind request information and the assembly redirect information in the assembly bind history file comprises uniquely identifying the assembly bind request information and the assembly redirect information in the assembly bind history file.

44. The computer-implemented method of claim 1, further comprising marking the assembly bind request information and the assembly redirect information in the assembly bind history file as sharable.

2-15. -15. (canceled)

16. A computer-readable medium having computer-executable instructions for performing steps, comprising:

recording assembly bind information referenced in an application being executed on a computer;

determining if the assembly bind information should be persisted in an assembly bind history file;

persisting the assembly bind information in the assembly bind history file when the step of determining is affirmative; and

binding all assemblies for the application in accordance with the assembly bind history file.

17-18. -18. (canceled)

19. A computer-readable medium having stored thereon a data structure, comprising a first data field containing temporal data relating to an assembly bind of an application, a second data field containing assembly name data for an assembly for which the application completed a bind request;

and a third data field associated with the second data field containing assembly bind information for each stage of assembly bind policy.

21. The data structure of claim 19, further comprising a fourth data structure containing data identifying the application.

20. (canceled)

22-28. -28. (canceled)