See central package management for working with packages across solutions.
rather than having them be project references inside the solution?
No
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am working with a very large legacy application. In recent years we have worked to separate the monolithic solution into multiple modules, each with its own VS solution and each stored in its own git repository with each solution generating nuget packages when it is built. The front-end solution then uses the nuget packages for references to our other modules. However, this often results in issues for the developers when changes or debugging need to happen across the multiple modules.
With VS 2022 supporting a solution having projects from multiple git repositories, is there a way that this solution can also have the inter-project references be handled as nuget packages (which would be generated locally each time the solution/project builds) rather than having them be project references inside the solution? This would allow us to have our front-end solution include the module projects and allow the VS refactoring and debugging tools to directly see the sources of the multiple modules.
TIA
See central package management for working with packages across solutions.
rather than having them be project references inside the solution?
No