dotnet / project-system

The .NET Project System for Visual Studio
MIT License
969 stars 387 forks source link

Ability to swap between package and project dependency #195

Open BillHiebert opened 8 years ago

BillHiebert commented 8 years ago

In .net Core this is done using the sources element in global.json

davkean commented 8 years ago

XLarge right now because we don't know what the design is, or how it will work.

Nirmal4G commented 4 years ago

This could be combined with #222 -- Since you need to specify only the name of the Project/Package (if assumed to be the same) and #197 -- You need to have a root folder from which all the projects in a solution could be placed and referenced from.

kvenkatrajan commented 1 year ago

Closing - xproj deprecated

drewnoakes commented 1 year ago

This would be helpful for solutions that both produce and consume their own NuGet packages. It's not specific to xproj per se.

Nirmal4G commented 1 year ago

@kvenkatrajan Please don't close issues when they very well can be applied to present products and services. I'm aware that these could have been created in the time of xproj era and might not have enough attention. If you really need to cleanup then please mark as stale, backlog instead of closing it.

kvenkatrajan commented 1 year ago

Thanks @Nirmal4G. My apologies - I made the assumption that this request was specific to xproj. Removing the parity-xproj and will rediscuss this in triage.

CC: @mckennabarlow