View source for 18300356. CENTRAL PACKAGE MANAGEMENT (CPM) ACROSS CODE REPOSITORIES simplified abstract (Microsoft Technology Licensing, LLC)

=CENTRAL PACKAGE MANAGEMENT (CPM) ACROSS CODE REPOSITORIES=


==Organization Name==

[[:Category:Microsoft Technology Licensing, LLC|Microsoft Technology Licensing, LLC]]


[[Category:Microsoft Technology Licensing, LLC]]

==Inventor(s)==

[[:Category:Eliyahu Mashhadi Kalimi of Netanya (IL)|Eliyahu Mashhadi Kalimi of Netanya (IL)]][[Category:Eliyahu Mashhadi Kalimi of Netanya (IL)]]

[[:Category:Roei Shlomo Menashof of Natanya (IL)|Roei Shlomo Menashof of Natanya (IL)]][[Category:Roei Shlomo Menashof of Natanya (IL)]]

[[:Category:David Mansour of Yehud (IL)|David Mansour of Yehud (IL)]][[Category:David Mansour of Yehud (IL)]]

==CENTRAL PACKAGE MANAGEMENT (CPM) ACROSS CODE REPOSITORIES - A simplified explanation of the abstract==


This abstract first appeared for US patent application 18300356 titled 'CENTRAL PACKAGE MANAGEMENT (CPM) ACROSS CODE REPOSITORIES

'''Simplified Explanation''': 

Central package management (CPM) allows for the automatic propagation of changes to package versions across multiple software projects in different code repositories. 

* Central package management system across code repositories
* Primary "props" file in a Git submodule references a version of a NuGet package
* Root directory of each code repository contains a props file that references the primary props file in the Git submodule
* Software projects in the code repositories have a package reference to the NuGet package without specifying the version
* Build process automatically uses the version of the NuGet package identified in the Git submodule
* Single change to the version number of the NuGet package in the Git submodule affects multiple projects in different repositories

'''Potential Applications''': 

This technology can be applied in large-scale software development projects where multiple projects across different repositories need to maintain consistency in package versions.

'''Problems Solved''': 

- Ensures consistency in package versions across multiple software projects
- Simplifies the process of updating package versions in a centralized manner

'''Benefits''': 

- Streamlines package management in complex software development environments
- Reduces the risk of version conflicts and inconsistencies across projects

'''Commercial Applications''': 

Central package management technology can be utilized by software development companies working on large projects with multiple repositories to improve efficiency and maintain consistency in package versions.

'''Questions about Central Package Management''':
 
1. How does central package management help in maintaining consistency across multiple software projects?
2. What are the key advantages of using a central package management system in software development projects?


==Original Abstract Submitted==

Central package management (CPM) across code repositories is disclosed. In an example, a primary “props” file in a Git submodule references a version of a NuGet package. A “.props” file in a root directory of each of multiple code repositories references the primary props file in the Git submodule. Each of multiple software projects in the code repositories has a package reference to the NuGet package without a reference to the version of the NuGet package. When each of the multiple the software projects is built (e.g., compiled), the build process automatically uses the version of the NuGet package that is identified in the Git submodule. This permits a single change to the version number of the NuGet package in the Git submodule to be propagated across multiple projects spanning multiple code repositories.



[[Category:G06F8/71]]
[[Category:G06F8/36]]
[[Category:CPC_G06F8/71]]