| Reporter |
Michael Scrivo (mscrivo)
|
|---|---|
| Created | Oct 16, 2017 9:32:38 PM |
| Updated | Apr 11, 2018 7:47:10 AM |
| Subsystem | Solution builder |
| Assignee | Anton Spilnyy (Anton.Spilnyy) |
| Priority | Normal |
| State | Submitted |
| Type | Bug |
| Fix version | No Fix versions |
| Affected versions | No Affected versions |
| Fixed In Version ReSharper | Undefined |
| VsVersion | All Versions |
We've recently switched all of our nuget packages to use PackageReferences instead of packages.config because of all the tooling issues they introduced in VS2017 15.3 regarding .NET standard and traditional .NET framework apps. (see https://github.com/dotnet/standard/issues/481 for details). Anyhow, what we discovered is that our beloved ReSharper build does not restore any packages that use the PackageReference format. It essentially ignores them. So you end up having to switch back to VS build whenever there are nuget package changes to get it to build properly.