Hi!

After changing a csproj-file to new format:
---

---
my Visual Studio 2017 v.15.6.4 compiles and runs just fine,
but NCrunch gives build error and reports:


How can I resolve this? I'm using NCrunch 3.12.0.15

Regards, Richard

Hi again,

and thanks for the swift reply.

The problem still persists, even after trying the steps you mentioned above.

There is also now an extra line reported in NCrunch, which is an extra project failing to build, reported for netstandard 1.3:

C:\Program Files\dotnet\sdk\2.1.103\Sdks\Microsoft.NET.Sdk\build\Microsoft.PackageDependencyResolution.targets: Assets file 'C:\Users\Someuser\AppData\Local\NCrunch\26492\2\Someproject\obj\project.assets.json' doesn't have a target for '.NETStandard,Version=v1.3'. Ensure that restore has run and that you have included 'netstandard1.3' in the TargetFrameworks for your project.

Yeah, I reproduced the error in a small solution, with one console-project having net461, referencing a simple class library project which I tried with the different project setup-possibilities as described below.
Also got fixtures for ncrunch, in a class library with net461, referencing the aforementioned simple class library.

Gives error:

<TargetFramework>netstandard1.3</TargetFramework>
<TargetFrameworks>netstandard2.0;net461</TargetFrameworks>
<TargetFrameworks>netstandard1.3;net461</TargetFrameworks>

Runs OK:

<TargetFramework>netstandard2.0</TargetFramework>
<TargetFramework>net461</TargetFramework>

I also sent in a zip with the reproduced VS solution through the support online contact form.

Thanks for the sample solution! Interestingly, this sample seems to work correctly in my own environment. So there must be an environmental component to this somewhere.

If global.json is needed in your environment for the projects to build, it's possible that this file isn't being included in the NCrunch workspace. If this is indeed the case, you may be able to solve the problem by adding it to the 'Additional files to include' setting for your solution.

I think that something in the MS tool stack is going wrong somehow here. It's possible the problem is tied to the versions of the .NET Core/Standard SDK that are installed on your machine. The newer SDKs seem to have a large number of moving parts making troubleshooting them very difficult. Let me know if the global.json inclusion doesn't solve the issue, and we'll try a few other things.