Versioning support in object-oriented programming languages and tools

• US 20050177826A1
• Filed: 02/05/2004
• Published: 08/11/2005
• Est. Priority Date: 02/05/2004
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Dussud, Patrick, Evans, William George, Miller, James S., Hawkins, Jonathan C., Parthasarathy, Srivatsan, Rivard, John J., Williams, Antony Scott, Hodges, C. Douglas, Szyperski, Clemens
• Application Number:
  US10/772,992
• Publication Number:
  US 20050177826A1
• Time in Patent Office: Days
• US Class Current: 717/170
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/44536 Selecting among different versions

Abstract

A versioning policy included in a target component indicates how the target component is to be accessed, for example, either as a library component or a platform component. A component may be designated as a library component when it is not versioned in a binary compatible manner. When other components request such a component they receive specifically the version of the component they requested. On the other hand, a component may be designated as a platform component when it is versioned in a binary compatible manner. When other components request such a component they may receive the latest upgraded version of the component requested instead. Thus, access to an appropriate version of the component (even a version differing from the requested version) is facilitated. Other embodiments include mechanisms for stratifying component scope based on different processing levels.

Claims

1. In a computerized system that includes one or more program components including one or more requesting components that can request to access one or more target components, a method of providing a requesting component with access to an appropriate version of a target component, comprising the acts of:

receiving a request to access a specified version of a target component, the request being received from a requesting component;

identifying a versioning policy of the specified version of the target component;

identifying an appropriate version of the target component based on the versioning policy of the specified target component;

providing the requesting component with access to the appropriate version of the target component.

2. The method as recited in claim 1, wherein the requested version of the target component is one of a library component and a platform component.

3. The method as recited in claim 1, wherein identifying an appropriate version of the target component comprises identifying a more recent version of the target component in response to a request for an earlier version of the target even though the more recent version and the earlier version are both accessible to the computerized system.

4. The method as recited in claim 3, identifying a more recent version of the target component in response to a request for an earlier version of the target even though the more recent version and the earlier version are both accessible to the computerized system comprises identifying a more recent version of a platform component even though an earlier version of the platform component remained on the system when the more recent version was received at the computerized system.

5. The method as recited in claim 1, wherein the versioning policy of the specified version of the target component is identified when the target component is one or more of compiled, configured, installed, and run on the computerized system.

6. The method as recited in claim 1, wherein version information that identifies the specified target component is stored in the requesting component when the requesting component is one or more of compiled, configured, installed, and run on the computerized system.

7. The method as recited in claim 1, further comprising:

identifying one or more requesting components that are able to access a prior version of the target component;

identifying that none of the one or more requesting components are configured to access the prior version of the target component; and

deleting the prior version of the target component.

8. The method as recited in claim 1, wherein the appropriate version of the target component is the version of the target component that was requested.

9. The method as recited in claim 1, wherein the appropriate version of the target component is different from the version of the target component that was requested.

10. The method as recited in claim 9, wherein target component access is provided to the requesting component through a determining module.

11. The method as recited in claim 10, wherein the availability of one or more of the prior version of the target component and the more recent version of the target component is identified by a determining module when the one or more of the prior version of the target component and the more recent version of the target component is received by the computerized system.

12. The method as recited in claim 1, wherein the versioning policy is inserted into computer-executable instructions in the target component prior to one of installing, configuring, and executing the target component on the computerized system.

13. The method as recited in claim 1, wherein the versioning policy is further identified in any version of the target component.

14. The method as recited in claim 13, wherein the versioning policy identifies that any of the prior version of the target component and the more recent version of the target component is configured to be accessed by a specific version of the requesting component.

15. The method as recited in claim 1, further comprising identifying a component scope that is associated with the target component.

16. The method as recited in claim 15, wherein access to the specified version of the target component is further based on one of the identified component scope associated with the target component, and a target component scope supplied by a system administrator.

17. The method as recited in claim 16, wherein the identified component scope specifies that access to the specified version of the target component is provided in one or more of a machine level, a process level, and a sub-process level.

18. The method as recited in claim 1, wherein the requested target component is a library component, the method further comprising identifying a servicing value associated with the requested target component.

19. The method as recited in claim 1, wherein identifying an appropriate version of the target component comprising identifying an updated version of a library component based on the identified versioning policy and the identified servicing value.

20. In a computerized system that includes one or more program components including one or more requesting components that can request to access one or more target components, a method of providing a requesting component with access to an appropriate version of a target component, comprising:

an act of receiving a request to access a specified version of a target component, the request being received from a requesting component;

a step for allowing access to an appropriate version of the requested target component such that the requesting component accesses the appropriate target component as it has been configured to do so, and such that the requesting component does not fail when requesting access to a component that has been upgraded.

21. The method as recited in claim 20, wherein the step for allowing access to an appropriate version of the requested target component comprises the corresponding acts of:

identifying a versioning policy of the specified version of the target component;

receiving a request to access a specified version of a target component, the request begin received from a requesting component;

providing the requesting component with access to the appropriate version of the target component.

22. In a computerized system that includes one or more program components including one or more requesting components that can request to access one or more target components, a method of upgrading a target component such that a requesting component that accesses the target component continues to operate effectively after the target component has been upgraded, comprising the acts of:

identifying that a requesting component is configured to access a target component;

identifying a versioning policy in at least an existing version of the target component and a previously installed version of the target component; and

identifying which versions of the target component should remain on the system based on any identified versioning policy corresponding to at least the existing version of the target component and the previously installed version of the target component.

23. The method as recited in claim 22, further comprising receiving an updated version of the target component over a network from a network service provider.

24. The method as recited in claim 22, wherein, if the versioning policy indicates that the requesting component is a library component, adding the existing version of the target component to the system without removing the previously installed version of the target component.

25. The method as recited in claim 22, wherein, if the versioning policy indicates that the requesting component is a platform component, overwriting the previously installed version of the target component with the existing version of the target component.

26. In a computerized system including one or more requesting components that are configured to access one or more source components, a computer program product having computer-executable instructions stored thereon that, when executed, cause the computerized system to perform a method of providing a requesting component with access to an appropriate version of a target component, comprising the acts of:

receiving a request to access a specified version of a target component, the request being received from a requesting component;

identifying a versioning policy of the specified version of the target component;

identifying an appropriate version of the target component based on the versioning policy of the specified target component;

providing the requesting component with access to the appropriate version of the target component.

27. In a computerized system including one or more requesting components that are configured to access one or more source components, a computer program product having computer-executable instructions stored thereon that, when executed, cause the computerized system to perform a method of upgrading a target component such that a requesting component that accesses the target component continues to operate effectively after the target component has been upgraded, comprising the acts of:

identifying that a requesting component is configured to access a target component;

identifying a versioning policy in at least an existing version of the target component and a previously installed version of the target component; and

identifying which versions of the target component should remain on the system based on any identified versioning policy corresponding to at least the existing version of the target component and the previously installed version of the target component.