Support the new PackageReference nodes in VS 2017 project files.
Currently NCrunch can't build projects that use the new PackageReference structure for NuGet packages as opposed to the "old" packages.config.
Workaround is to use the old method.
We implemented this a few years ago, to avoid breaking the entire world under NCrunch (as these references are everywhere now).
Closing this task as I think we’re good here.
Richard Cooper commented
Having the same issue :( this is the new PackageReference style in a Full Framework .NET class library.
Interestingly, this seems to be a regression in v3.3.
It did actually work in v3.2.
I'm not sure what has changed to break this, but I'm planning to investigate and release a fix for it soon.
Thijs Tijsma commented
Apparently I can't edit the feature request, but I forgot to mention this happens in regular .NET projects (4.6.2).