US 12,086,588 B2
Application module version management
Akhil Gupta, Redmond, WA (US); Abhinav Jha, Redmond, WA (US); Prabhat Kumar Pandey, Redmond, WA (US); Abhishek Agarwal, Redmond, WA (US); and Yasser Shaaban, Redmond, WA (US)
Assigned to Microsoft Technology Licensing, LLC, Redmond, WA (US)
Filed by Microsoft Technology Licensing, LLC, Redmond, WA (US)
Filed on Jan. 30, 2023, as Appl. No. 18/161,425.
Application 18/161,425 is a continuation of application No. 17/353,463, filed on Jun. 21, 2021, granted, now 11,599,355.
Prior Publication US 2023/0251855 A1, Aug. 10, 2023
This patent is subject to a terminal disclaimer.
Int. Cl. G06F 8/71 (2018.01); G06F 8/41 (2018.01)
CPC G06F 8/71 (2013.01) [G06F 8/433 (2013.01)] 18 Claims
OG exemplary drawing
 
1. A method of managing versions of an application, comprising:
assembling a first version of the application based on a first version of a master application component, a relationship operable to relate the first version of the master application component with a corresponding version of a first component on which the master application component depends for a function of the application, and the corresponding version of the first component;
validating, using a graphical representation of the application, that a different version of the first component functions with the application based on metadata associated with the different version of the first component;
determining a difference between a different version of the application and the first version of the application, wherein the difference includes the different version of the first component, the different version of the first component including metadata associated with the different version of the first component;
storing, the metadata associated with the different version of the first component with a reference to the different version of the first component and a corresponding reference to the different version of the master application component;
storing, a second relationship, wherein the second relationship is operable to relate the different version of the first component with the different version of the master application component; and
assembling, based on the second relationship, a different version of the application based on a different version of the master application component and the different version of the first component.