Package management is messy and tedious where we have variables to set version numbers of packages. We then need to manually update package versions to reference those variables in all .csproj files. When a package needs an update, it reverts the variable in the .csproj file to a version number requiring us to go and manually update the version number again.
Security review preparation requires us to document and track all OSS components, containers, and code. We must also demonstrate that dependencies are currently approved by Microsoft OSS for use in our project.
- To address this, having a central location to easily update and manage package dependencies is desirable.
Package management is messy and tedious where we have variables to set version numbers of packages. We then need to manually update package versions to reference those variables in all .csproj files. When a package needs an update, it reverts the variable in the
.csprojfile to a version number requiring us to go and manually update the version number again.Security review preparation requires us to document and track all OSS components, containers, and code. We must also demonstrate that dependencies are currently approved by Microsoft OSS for use in our project.