US 12,032,950 B2
Embedding code from modules across versioning boundaries
David Charles Wrighton, Redmond, WA (US); Anton Lapounov, Kirkland, WA (US); Tomás Rylek, Suchdol (CZ); and Jan Kotas, Redmond, WA (US)
Filed by Microsoft Technology Licensing, LLC, Redmond, WA (US)
Filed on Oct. 4, 2022, as Appl. No. 17/960,058.
Prior Publication US 2024/0111518 A1, Apr. 4, 2024
Int. Cl. G06F 9/44 (2018.01); G06F 8/41 (2018.01); G06F 8/654 (2018.01); G06F 8/71 (2018.01); G06F 11/36 (2006.01); G06F 11/34 (2006.01)
CPC G06F 8/654 (2018.02) [G06F 8/4443 (2013.01); G06F 8/71 (2013.01); G06F 8/441 (2013.01); G06F 8/443 (2013.01); G06F 8/4434 (2013.01); G06F 8/447 (2013.01); G06F 11/3419 (2013.01); G06F 11/3628 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A computing system comprising:
one or more processors; and
one or more computer-readable hardware storage devices having stored thereon computer-executable instructions that are structured such that, when executed by the one or more processors, the computer-executable instructions cause the computing system to perform at least:
an inline expansion process that copies a first method from a first software component into a first method of a second software component so that the copied first method is executable when the first method of the second software component is executed;
copying the first method from the first software component into metadata that is attached to the first method of the second software component; and
using the copy of the first method in the metadata to validate that the first method in the first software component has not been updated after the inline expansion process has occurred.