You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When interacting with deep dependency tree of opensource libraries, or even internal projects, that are referenced from nuget packages, it is very tedious and error prone process, when one desire to step debug and update code in more than one of the repositories / solutions.
One has to do so by replacing the package references to either assembly or project references, or to deploy updated nuget package.
I'm looking for a solution that would enable allow to clone or refer to a clone of each such dependency, and would enable to do dotnet build/run/test/etc. against such tree where a set of nuget references would be replaced with the project references.
The feature would work by defining for each PackageReference name that needs to be processed, either:
a local folder
the uri to the repository (msbuild would orchestrate clone to a stable temporary folder)
nothing
given the are build subtleties in each project, and potentially several .sln, the nuget packages would need to embed:
build step information for such scenario, probably as a list of sanitized dotnet commands
the .sln for such scenario (for the in IDE experience)
In the IDE, it would manifest as if the solution explorer had one more level with top nodes being the sln.
This would boost productivity in those circumstances, and encourage more evolution between synergistic projects.
The text was updated successfully, but these errors were encountered:
When interacting with deep dependency tree of opensource libraries, or even internal projects, that are referenced from nuget packages, it is very tedious and error prone process, when one desire to step debug and update code in more than one of the repositories / solutions.
One has to do so by replacing the package references to either assembly or project references, or to deploy updated nuget package.
I'm looking for a solution that would enable allow to clone or refer to a clone of each such dependency, and would enable to do
dotnet build/run/test/etc.
against such tree where a set of nuget references would be replaced with the project references.The feature would work by defining for each PackageReference name that needs to be processed, either:
given the are build subtleties in each project, and potentially several .sln, the nuget packages would need to embed:
dotnet
commandsIn the IDE, it would manifest as if the solution explorer had one more level with top nodes being the sln.
This would boost productivity in those circumstances, and encourage more evolution between synergistic projects.
The text was updated successfully, but these errors were encountered: