Unable to run tests with .NET Core 2.0 referencing .NET Standard 2.0

I've prepared a new build including what I hope is a fix for this issue. Would you be interested in giving it a try?

http://downloads.ncrunch.net/NCrunch_Console_3.11.0.6.msi
http://downloads.ncrunch.net/NCrunch_Console_3.11.0.6.zip
http://downloads.ncrunch.net/NCrunch_GridNodeServer_3.11.0.6.msi
http://downloads.ncrunch.net/NCrunch_GridNodeServer_3.11.0.6.zip
http://downloads.ncrunch.net/NCrunch_LicenseServer_3.11.0.6.zip
http://downloads.ncrunch.net/NCrunch_VS2008_3.11.0.6.msi
http://downloads.ncrunch.net/NCrunch_VS2010_3.11.0.6.msi
http://downloads.ncrunch.net/NCrunch_VS2010_3.11.0.6.zip
http://downloads.ncrunch.net/NCrunch_VS2012_3.11.0.6.msi
http://downloads.ncrunch.net/NCrunch_VS2012_3.11.0.6.zip
http://downloads.ncrunch.net/NCrunch_VS2013_3.11.0.6.msi
http://downloads.ncrunch.net/NCrunch_VS2013_3.11.0.6.zip
http://downloads.ncrunch.net/NCrunch_VS2015_3.11.0.6.msi
http://downloads.ncrunch.net/NCrunch_VS2015_3.11.0.6.zip
http://downloads.ncrunch.net/NCrunch_VS2017_3.11.0.6.msi
http://downloads.ncrunch.net/NCrunch_VS2017_3.11.0.6.zip

Thanks for the new build. No change, unfortunately. Does seem to take longer to reach point of failure though (anecdotal only, have no measurements).

sextondjc wrote:Thanks for the new build. No change, unfortunately. Does seem to take longer to reach point of failure though (anecdotal only, have no measurements).

I'm sorry to hear that :( Has the primary error in the log changed at all? (i.e. System.Threading.Thread library). Are you still able to produce the issue consistently with a new sample project?

I appear to be hitting a similar issue in trying to use Net Core 2.0

I tried both 3.11.0.5 and 3.11.0.6, to no avail.

I did submit a bug report, so the data should be there for you, Remco.

Let me know if I might help further.

Cameron

NCrunch encountered an error while trying to construct an environment to execute this test: nCrunch.TaskRunner.Ipc.IpcConnectionClosedException: The connection has been closed
at nCrunch.Core.ProcessManagement.ExternalProcessManager.(ProcessorArchitecture , ProcessLoadParameters )
at nCrunch.Core.ProcessManagement.ExternalProcessManager.LoadExternalProcess(ProcessLoadParameters parameters, GridClientId client)
at nCrunch.Core.TestManagement.TestRunnerProcess..()
at nCrunch.Common.PerformanceTracking.PerfTracker.TrackActivity(String name, Action activity)
at nCrunch.Core.TestManagement.TestRunnerProcess.(Nullable`1 , FilePath , GridClientId , CustomEnvironmentVariable[] )
at nCrunch.Core.TestManagement.TestRunnerProcess..()
at nCrunch.Common.PerformanceTracking.PerfTracker.TrackActivity(String name, Action activity)
at nCrunch.Core.Processing.TestExecutionTaskLogic.DoProcessTaskAndReturnSuccessFlag()

I sent a bug report with a Sysinternals/Procmon capture file, filtering on procname=*crunch*, in the event it is helpful.
[I ran this, and reviewed it, but it wasn't clear to me what the issue might be]

Thanks Cameron, it looks like this is still the System.Threading.Thread issue under the hood:

System.Exception: Could not resolve assembly: System.Threading.Thread, Version=4.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3aSystem.IO.FileNotFoundException: Could not load file or assembly 'System.Threading.Thread, Version=4.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.
File name: 'System.Threading.Thread, Version=4.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'

I've had another stab at this problem. It's all speculative, unfortunately, as this problem seems to be tied to install state. Would you like to try the build below to see if this works better?

http://downloads.ncrunch.net/NCrunch_Console_3.11.0.8.msi
http://downloads.ncrunch.net/NCrunch_Console_3.11.0.8.zip
http://downloads.ncrunch.net/NCrunch_GridNodeServer_3.11.0.8.msi
http://downloads.ncrunch.net/NCrunch_GridNodeServer_3.11.0.8.zip
http://downloads.ncrunch.net/NCrunch_VS2017_3.11.0.8.msi
http://downloads.ncrunch.net/NCrunch_VS2017_3.11.0.8.zip

That didnt do it.
Installed, and verified version 3.11.0.8 from the menu.
I will do a little looking around on this PC and report back.

NCrunch encountered an error while trying to construct an environment to execute this test: nCrunch.TaskRunner.Ipc.IpcConnectionClosedException: The connection has been closed
at nCrunch.Core.ProcessManagement.ExternalProcessManager.(ProcessorArchitecture , ProcessLoadParameters )
at nCrunch.Core.ProcessManagement.ExternalProcessManager.LoadExternalProcess(ProcessLoadParameters parameters, GridClientId client)
at nCrunch.Core.TestManagement.TestRunnerProcess..()
at nCrunch.Common.PerformanceTracking.PerfTracker.TrackActivity(String name, Action activity)
at nCrunch.Core.TestManagement.TestRunnerProcess.(Nullable`1 , FilePath , GridClientId , CustomEnvironmentVariable[] )
at nCrunch.Core.TestManagement.TestRunnerProcess..()
at nCrunch.Common.PerformanceTracking.PerfTracker.TrackActivity(String name, Action activity)
at nCrunch.Core.Processing.TestExecutionTaskLogic.DoProcessTaskAndReturnSuccessFlag()

Sorry to hear that. Can you check the following:

1. Open the NCrunch Tests Window
2. Right click on the project containing the failing test
3. Go to advanced -> Browse to workspace
4. Find the directory containing the DLL (i.e. bin\debug)
5. Find the file nCrunch.TaskRunner.DotNetCore.20.x64.runtimeconfig.dev.json, open this in notepad
6. The file should point to 3 different package search locations
7. Can you verify which versions of System.Threading.Thread are installed in these 3 locations?

Remco,

There are three folders in that file:
"C:\\Users\\cameron\\.dotnet\\store\\|arch|\\|tfm|",
"C:\\Users\\cameron\\.nuget\\packages",
"C:\\Program Files\\dotnet\\sdk\\NuGetFallbackFolder"

here are the files:
External image

I only checked the 41Kb file's ver&key, and it has the correct version and key.

But, if the correct file must be 41kb, none of the others probably are the correct version or pubkey.

So, it looks like the only correct file is C:\Program Files\dotnet\shared\Microsoft.NETCore.App\2.0.0\System.Threading.Thread.dll

Cameron

Thanks Cameron.

Could you try adding a Nuget package dependency on System.Threading.Thread.dll v4.3.0 to see if this suppresses the problem?

Also, is there any chance I could see the contents of the nCrunch.TaskRunner.DotNetCore.20.x64.deps.json file inside the NCrunch workspace? I realise there's a bit of content in there .. you're welcome to put the file through the contact form if you find this convenient.

Remco,

Adding the nuget ref you specified fixed the issue.
I submitted the file contents through the form.

Thanks for working on this so diligently.
I guess when my trial is up I have to buy a copy now!
I can see how I can get pretty dependent on NCrunch, even after using it a short time, and not really historically being a TDD guy.
One thing that is interesting, is I have <known> about NCrunch for a few years, but
I saw a recent announcement for the VS2017 Enterprise NCrunch-like feature, but
after weighing everything out, I decided if I wanted to start using live unit tests I should probably go with NCrunch.
So MSFT might be bringing you business by coming into the space. :)

Cameron

Thanks, good to know that the 4.3.0 dependency fixed it ... that's about the most sensible thing I've seen about this problem so far. I noticed that the file you submitted was done after the 4.3.0 dependency was added. Is there any chance I could have a copy of the same file without this dependency? I'd like to keep trying to reproduce this issue in the hope of introducing a solid fix for it.

Cameron wrote:
I can see how I can get pretty dependent on NCrunch, even after using it a short time, and not really historically being a TDD guy.
One thing that is interesting, is I have <known> about NCrunch for a few years, but
I saw a recent announcement for the VS2017 Enterprise NCrunch-like feature, but
after weighing everything out, I decided if I wanted to start using live unit tests I should probably go with NCrunch.
So MSFT might be bringing you business by coming into the space. :)
Cameron

I'm glad to hear that you're enjoying it :) I had expected that the MS announcement might help make people more aware of NCrunch. In a manner of speaking, it's a bit of a victory when a product's concept becomes so successful that they build it into the base platform. It's tough to know how many people are picking up NCrunch because of MS's entry into the sector, but I'll take all the good news I can get :)

I removed the dependency, and did a rebuild and the project went back to broken. I submitted the json file through the form.
Regards
Cameron

Same here does not work

i got a solution with 4 projects (WPF and .net standard)

the most basic .net standard project (having only a nuget depency to a .net standard project) doesnt build.

I also submitted an bug report


NCrunch: If you are experiencing problems in getting this project to build, have a look at http://www.ncrunch.net/documentation/troubleshooting_project-build-issues
System.ArgumentNullException: Der Wert darf nicht NULL sein.
Parametername: type
bei nCrunch.Compiler.StaticManipulation.StaticInstrumentationImportMethodSet..ctor(CustomCecilAssemblyResolver resolver, ModuleDefinition module)
bei nCrunch.Core.PlatformTypes.DotNetCorePlatformType.GetInstrumentationMethodsForFramework(CustomCecilAssemblyResolver resolver, AssemblyDefinition assembly)
bei nCrunch.Compiler.StaticManipulation.BuiltAssembly.Instrument(ComponentSourceLineMap sourceLineMap, IDictionary`2 instrumentationDirectivesByCodeFileId, IDictionary`2 codeFileIDsByFilePath, Boolean proxyProcessIsActive, Int32 componentId, IInstrumentationFilter[] instrumentationFilters, IBuildPlatformType platformType, PerfTracker perfTracker)
bei nCrunch.Compiler.RemoteBuildRunner.(ComponentBuildParameters , FilePath , BuildOutput , DirectoryPath[] , FilePath[] )
bei nCrunch.Compiler.RemoteBuildRunner..()
bei nCrunch.Common.PerformanceTracking.PerfTracker.TrackActivity(String name, Action activity)
bei nCrunch.Compiler.RemoteBuildRunner.(ComponentBuildParameters )


Project file looks like that:

<Project Sdk="Microsoft.NET.Sdk">

<PropertyGroup>
<TargetFramework>netstandard2.0</TargetFramework>
</PropertyGroup>

<ItemGroup>
<PackageReference Include="BE.CQRS" Version="0.20.0-alpha" />
</ItemGroup>

</Project>

Btw the project i have trouble with doesnt have any sensitive data and is a spare time project by me. So i could add you in github to the project. if it would be of any help

Hi BoasE,

Thanks for posting. Have tried the latest test build published earlier in this thread? The problem you're experiencing is something that should already be solved in the test builds and is due to be released next week.

I Installed NCrunch_Console_3.11.0.8.msi

is there anything I should to further?

BoasE wrote:I Installed NCrunch_Console_3.11.0.8.msi

is there anything I should to further?

If you're using NCrunch inside VS, you should also install the VS2017 package. These builds are basically just the same as the production builds on the main download page, expect they usually haven't seen quite the same level of testing or real world exposure.

Perfect. I can confirm that it works now ! Thx !