How to seamlessly swap NuGet packages with source?

[MartinJohns]

In the past you demonstrated a way to seamlessly replace referenced NuGet packages with the actual source of projects by simply cloning the source code of the NuGet package to a path that is referenced in the global.json file, without any further change required.

How is this behavior possibly with the new MSBuild tooling? Looking at the csproj file I can see that there are now distinct values for ProjectReference and PackageReference, unlike previously only a dependency in the project.json. I also see no global.json file anymore when creating a new project. Do I now need to manually reference all projects to my solution and swap out the PackageReference with the ProjectReference node?

[cwe1ss]

related to #1151

As I've said there, I'd love to see this solved in a way that doesn't touch committed files. With global.json, it was easy to mistakenly commit the local paths.

[andycmaj]

curious what people think of this naive approach: #1151 (comment)

[github-actions]

Due to lack of recent activity, this issue has been labeled as 'stale'. It will be closed if no further activity occurs within 30 more days. Any new comment will remove the label.

[github-actions]

This issue will now be closed since it has been labeled 'stale' without activity for 30 days.