| Reporter |
Rian Stockbower (rianjs)
|
|---|---|
| Created | Nov 15, 2017 6:21:05 PM |
| Updated | Apr 11, 2018 5:37:18 PM |
| Subsystem | Optimize References |
| Assignee | Alexander Ulitin (alexander.ulitin) |
| Priority | Normal |
| State | Submitted |
| Type | Bug |
| Fix version | 2017.3 |
| Affected versions | No Affected versions |
| Fixed In Version ReSharper | Undefined |
| VsVersion | All Versions |
nuget now has two resolution mechanisms, as you probably know.
This is problematic for mixing and matching Framework and NetStandard libraries. The PackageReference entry will compute the dependency graph, and pull down everything it needs automagically. If you use the old packages.config way, you have to flatten the dependency graph into the packages.config file, and manually reference each required DLL.
Immo Landwerth has basically said that PackageReference is the future. It would be nice to have support for it:
https://github.com/dotnet/standard/issues/481
- packages.config + references to assemblies on disk. This works fine, as always.
-
PackageReferenceentries in a csproj file. This doesn't work.
This is problematic for mixing and matching Framework and NetStandard libraries. The PackageReference entry will compute the dependency graph, and pull down everything it needs automagically. If you use the old packages.config way, you have to flatten the dependency graph into the packages.config file, and manually reference each required DLL.
Immo Landwerth has basically said that PackageReference is the future. It would be nice to have support for it:
https://github.com/dotnet/standard/issues/481