Method and systems for DLL/COM redirection

• US 6,976,037 B1
• Filed: 06/27/2000
• Issued: 12/13/2005
• Est. Priority Date: 03/27/2000
• Status: Expired due to Term

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: D'Souza, David J., Wilson, Peter M., FitzSimons, RoseMarie, Harikrishnnan, Seetharaman
• Primary Examiner(s): Pardo, Thuy N.
• Application Number:
  US09/605,137
• Time in Patent Office: 1,995 Days
• Field of Search: 707/203, 707/10, 707/102, 707/104, 707/511, 717/170, 717/172, 717/2, 717/1, 709/11, 709/246, 709/305, 703/26, 713/200
• US Class Current: 1/1
• CPC Class Codes: G06F 9/44536 Selecting among different versions
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

Methods, systems and data structure are described for implementing local isolated DLL and/or COM components. A version of a shared component is stored in a local directory with an application that uses that particular version. Another version of the shared component exists on the system and is useable by any number of other computer programs. A local file is created in the local directory that indicates the presence of an isolated version of the shared component. When the application calls the shared component, the system uses the isolated version of the shared component stored locally with the application program. Thus, specific versions of components may be provided to a calling application without making any code changes to the calling application or to the Component to which the calling application is bound.

Claims

1. A method comprising:

storing a computer application program in a first logical directory of one or more computer-readable media;

storing a first version of a shared component and a pointer indicator in the first logical directory for execution with the computer application program on a computer system that stores at least a second version of the shared component in a second logical directory of the one or more computer-readable media, wherein the shared component is a functional component of the computer application program that is compatible therewith; and

wherein the computer application program is configured to use the first version of the shared component and not the second version of the shared component when the computer application program is executed on the computer system based on the pointer indicator being present in the first logical directory.

2. The method as recited in claim 1, wherein the pointer indicator comprises at least a file name, the pointer indicator indicating to the computer application program that the first version of the shared component referenced by the pointer indicator is located in the first logical directory.

3. One or more computer readable media containing computer-executable instructions that, when executed on a computer, perform the following steps:

storing an application in a first directory of a computer system;

storing a local version of a shared program component in the first directory; and

installing a file that indicates to the application that the application should utilize the local version of the shared program component without regard for a second version of a shared program component stored in a second directory of the computer system; and

wherein the local version of the shared component is a functional component of the application that is compatible therewith.

4. A method, comprising:

calling a shared component in a computer system;

detecting a local file that indicates the presence of a locally-stored version of the shared component, the local file being a different file than the shared component itself; and

in response to detecting the local file, utilizing the locally-stored version of the shared component that is stored in a first directory of the computer system instead of a global version of the shared component present in a second directory of the computer system.

5. The method as recited in claim 4, further comprising searching for the local file when the shared component is called and, if the local file is not found, utilizing the global version of the shared component.

6. The method as recited in claim 4, wherein the local file is an empty file.

7. One or more computer readable media containing computer-executable instructions that, when executed by a computer, perform the following steps:

storing a computer application program in a first directory of a computer system that maintains a multiple-level directory structure;

storing a local version of a shared component in the first directory for execution with the computer application program on the computer system, the computer system storing at least another version of the shared component in a second directory of the computer system; and

wherein the computer application program is configured to utilize the local version of the shared component and not the other version of the shared component when the computer application program is executed on the computer.

8. The one or more computer readable media as recited in claim 7, the computer-executable instructions, when executed by a computer, further performing the step of storing a file in the first directory of the computer system that indicates the local version of the shared component is stored in the first directory.

9. The one or more computer readable media as recited in claim 7, wherein the shared component stored by the computer-executable instructions is a component object model (COM) component.

10. The one or more computer readable media as recited in claim 7, wherein the shared component stored by the computer-executable instructions is a dynamic-link library (DLL) component.

11. A computer system, comprising:

memory divided into a plurality of discrete memory partitions;

an application program stored in a first memory partition;

a first version of a shared component stored in the first memory partition, the first version of the shared component useable by the application program;

a second version of the shared component stored in a second memory partition;

an indicator stored in the first memory partition that, when present, indicates the existence of the first version of the shared component in the first memory partition; and

wherein the application program utilizes the first version of the shared component if the indicator is present.

12. A computer system as recited in claim 11, wherein the indicator includes a file having a name conforming to a predefined type.

13. A computer system as recited in claim 12, wherein the file is an empty file.

14. The computer system as recited in claim 11, wherein the shared component is a component object model (COM) component.

15. The computer system as recited in claim 11, wherein the shared component is a dynamic-link library (DLL) component.

16. One or more computer-readable media containing a directory tree data structure having multiple directories, comprising:

first directory that contains a pointer to a global version of a shared component useable by a plurality of computer programs;

a second directory that contains a pointer to an application program and a pointer to a local version of the shared component; and

wherein the application program utilizes the local version of the shared component when the application program calls the shared component.

17. The one or more computer-readable media as recited in claim 16, wherein the second directory further includes an indicator that indicates the existence of the local version of the shared component.

18. The one or more computer-readable media directory tree data structure as recited in claim 17, wherein the indicator includes a pointer to a file having a name of a pre-defined type.

19. The one or more computer-readable media directory tree data structure as recited in claim 16, wherein the shared component is a component object model (COM) component.

20. A method comprising:

storing a computer application program on one or more computer-readable media;

storing a first version of a shared component in the one or more computer-readable media for execution on a computer system that stores at least a second version of the shared component, wherein the first component is a functional component of the computer application program that is compatible therewith;

establishing a logical relationship between the computer application program and the first version of the shared component so that the application uses the first version of the shared component and not the second version of the shared component when the computer application program is executed on the computer system; and

wherein the establishing a logical relationship between the computer application program and the first version of the shared component includes configuring a logical directory data structure that has multiple logical directories so that the computer application program and the first version of the shared component are referenced within a first logical directory, and wherein the second version of the shared component is referenced within a second logical directory.