Visual Studio 16.8 RTM - NCrunch Error

After updating to VS 2019 16.8 (Enterprise) NCrunch only shows errors (we have a asp.net core 3.1 solution, about 40 c# projects) --> Full Framework Solutions (.net 4.7.2) seems to working fine in 16.8)

Restarting VS, restarting NCrunch (deleting the .obj folder or the .vs folder) does not solve the problem, also setting the instrumentation mode to legacy does not fix the problem.

We are using MSTest v2.

FYI: The VS test runner as well as the R# test runner are still working fine.

Going back to VS 2019 16.7.x fixes the problem.

Update: I also submited a bug via Visual Studio.


[20:31:23.3318-UI-1] getWindow for nCrunch.VSIntegration2010.TestsToolWindowPane
[20:31:50.2569-UI-1] getWindow for nCrunch.VSIntegration2010.TestsToolWindowPane
ENGINE - [20:31:51.0568-LocalTestExecutionTask-36] ERROR (Internal): nCrunch.TaskRunner.Ipc.IpcConnectionClosedException: The connection has been closed
at nCrunch.TaskRunner.Ipc.Fast.IpcReader.Initialise()
at nCrunch.TaskRunner.Ipc.Fast.IpcStream.Connect(String ipcName, Boolean isHost)
at nCrunch.TaskRunner.Ipc.Fast.FastIpcClient.Connect(String ipcName)
at nCrunch.Core.ProcessManagement.DefaultProcessLoader.ConnectToProcess(ExternalProcess externalProcess, ProcessLoadParameters parameters, Action`1 outOfBandMessageHandler)
at nCrunch.Core.ProcessManagement.ExternalProcessManager..()
at nCrunch.Common.PerformanceTracking.PerfTracker.TrackActivity(String name, Action activity)
at nCrunch.Core.ProcessManagement.ExternalProcessManager.(EffectiveProcessorArchitecture , ProcessLoadParameters )

ENGINE - [20:31:51.0588-LocalTestExecutionTask-36] nCrunch.TaskRunner.Ipc.IpcConnectionClosedException: The connection has been closed
at nCrunch.Core.ProcessManagement.ExternalProcessManager.(EffectiveProcessorArchitecture , 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 , CustomVariable[] )
at nCrunch.Core.TestManagement.TestRunnerProcess..()
at nCrunch.Common.PerformanceTracking.PerfTracker.TrackActivity(String name, Action activity)
at nCrunch.Core.TestManagement.TestRunnerProcess.LoadTestRunnerProcessForProjectReturningProcessId(SnapshotComponent snapshotComponent, IList`1 componentsInProcess, TestFrameworkDescription[] testingFrameworks, Nullable`1 newProcessTag, FilePath solutionFilePath, GridClientId client, CustomVariable[] customEnvironmentVariables)
at nCrunch.Core.Processing.TestExecutionTaskLogic.DoProcessTaskAndReturnSuccessFlag()
ENGINE - [20:31:51.4368-LocalTestExecutionTask-43] ERROR (Internal): nCrunch.TaskRunner.Ipc.IpcConnectionClosedException: The connection has been closed
at nCrunch.TaskRunner.Ipc.Fast.IpcReader.Initialise()
at nCrunch.TaskRunner.Ipc.Fast.IpcStream.Connect(String ipcName, Boolean isHost)
at nCrunch.TaskRunner.Ipc.Fast.FastIpcClient.Connect(String ipcName)
at nCrunch.Core.ProcessManagement.DefaultProcessLoader.ConnectToProcess(ExternalProcess externalProcess, ProcessLoadParameters parameters, Action`1 outOfBandMessageHandler)
at nCrunch.Core.ProcessManagement.ExternalProcessManager..()
at nCrunch.Common.PerformanceTracking.PerfTracker.TrackActivity(String name, Action activity)
at nCrunch.Core.ProcessManagement.ExternalProcessManager.(EffectiveProcessorArchitecture , ProcessLoadParameters )


Detailed log:
https://drive.google.com/file/d/1_-uI33xLMuEenupYAlLDix5vcqU3jvtY/view?usp=sharing

Btw we are using the latest NCrunch version (4.4.0.12)

Thanks for reporting this to us. We're looking into it.

michaelkroes wrote:Thanks for reporting this to us. We're looking into it.

I've seen Remco tweeted a release is prepared that will work with .net 5, will this bug also covered by this fix?
Br

Hi,

I'm not 100% sure this will be fixed with the next release. I can't reproduce it just yet. Would you mind giving this release a try? It should be released as the version that supports 16.8 and net5.0 soon:

NCrunch_Console_4.5.0.3.msi
NCrunch_Console_4.5.0.3.zip
NCrunch_GridNodeServer_4.5.0.3.msi
NCrunch_GridNodeServer_4.5.0.3.zip
NCrunch_LicenseServer_4.5.0.3.zip
NCrunch_VS2008_4.5.0.3.msi
NCrunch_VS2010_4.5.0.3.msi
NCrunch_VS2010_4.5.0.3.zip
NCrunch_VS2012_4.5.0.3.msi
NCrunch_VS2012_4.5.0.3.zip
NCrunch_VS2013_4.5.0.3.msi
NCrunch_VS2013_4.5.0.3.zip
NCrunch_VS2015_4.5.0.3.msi
NCrunch_VS2015_4.5.0.3.msi.7z
NCrunch_VS2015_4.5.0.3.zip
NCrunch_VS2017_4.5.0.3.msi
NCrunch_VS2017_4.5.0.3.msi.7z
NCrunch_VS2017_4.5.0.3.zip
NCrunch_VS2019_4.5.0.3.msi
NCrunch_VS2019_4.5.0.3.msi.7z
NCrunch_VS2019_4.5.0.3.zip

michaelkroes wrote:Hi,

I'm not 100% sure this will be fixed with the next release. I can't reproduce it just yet. Would you mind giving this release a try? It should be released as the version that supports 16.8 and net5.0 soon:

NCrunch_Console_4.5.0.3.msi
NCrunch_Console_4.5.0.3.zip
NCrunch_GridNodeServer_4.5.0.3.msi
NCrunch_GridNodeServer_4.5.0.3.zip
NCrunch_LicenseServer_4.5.0.3.zip
NCrunch_VS2008_4.5.0.3.msi
NCrunch_VS2010_4.5.0.3.msi
NCrunch_VS2010_4.5.0.3.zip
NCrunch_VS2012_4.5.0.3.msi
NCrunch_VS2012_4.5.0.3.zip
NCrunch_VS2013_4.5.0.3.msi
NCrunch_VS2013_4.5.0.3.zip
NCrunch_VS2015_4.5.0.3.msi
NCrunch_VS2015_4.5.0.3.msi.7z
NCrunch_VS2015_4.5.0.3.zip
NCrunch_VS2017_4.5.0.3.msi
NCrunch_VS2017_4.5.0.3.msi.7z
NCrunch_VS2017_4.5.0.3.zip
NCrunch_VS2019_4.5.0.3.msi
NCrunch_VS2019_4.5.0.3.msi.7z
NCrunch_VS2019_4.5.0.3.zip

unfortunately it's not fixed, can I help you somehow?
br

Sorry to hear that.

The log you supplied shows the test execution process dying. Would you mind checking the event viewer to see if there's any extra information about the crashing process?

If there's nothing there would you mind trying to create a small test project?

In the mean time I'll investigate some more on our end.

michaelkroes wrote:Sorry to hear that.

The log you supplied shows the test execution process dying. Would you mind checking the event viewer to see if there's any extra information about the crashing process?

If there's nothing there would you mind trying to create a small test project?

In the mean time I'll investigate some more on our end.

There is nothing in the windows event log, here is a sample project: https://drive.google.com/file/d/1oOhAS25exyyRYThs0n9g0PNnHiii6scl/view?usp=sharing

It only happens when I use a asp.net core web project :
Microsoft.NET.Sdk.Web


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

<PropertyGroup>
<TargetFramework>netcoreapp3.1</TargetFramework>
</PropertyGroup>


</Project>

When I use a non web project like so everything is working

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

<PropertyGroup>
<TargetFramework>netcoreapp3.1</TargetFramework>
</PropertyGroup>


</Project>

Thanks! I’ll give that a try and report back.

michaelkroes wrote:Thanks! I’ll give that a try and report back.

Please have look at the previous post, I found the reason, it <Project Sdk="Microsoft.NET.Sdk.Web">
br

Just to clarify, you do expect that sdk to work with NCrunch right? Because it works with VS an R#. Vs 2019 had some changes before in this area. Our old test case seem to pass.

michaelkroes wrote:Just to clarify, you do expect that sdk to work with NCrunch right? Because it works with VS an R#. Vs 2019 had some changes before in this area. Our old test case seem to pass.

Yes. <Project Sdk="Microsoft.NET.Sdk"> AND <Project Sdk="Microsoft.NET.Sdk.Web"> should work, it was working more or less I can remember and stopped yesterday after installing VS 2019 16.8.

br

Awesome. I’ll investigate.

michaelkroes wrote:Awesome. I’ll investigate.

thank you very much!

Btw. I also tried to reinstalled the .net sdk without luck.

I see from the solution cache that you had an error with the solution. But when I rebuild it on two different machines it works for me. I'm going to consult with Remco and see what we can try next.

michaelkroes wrote:I see from the solution cache that you had an error with the solution. But when I rebuild it on two different machines it works for me. I'm going to consult with Remco and see what we can try next.

thx

upper wrote:

michaelkroes wrote:I see from the solution cache that you had an error with the solution. But when I rebuild it on two different machines it works for me. I'm going to consult with Remco and see what we can try next.

thx

I found the problem:
I removed the 2019 16.8 Preview Version of VS than I repaired NCrunch (using the NCrunch Installer) and now everything is working fine again. --> I really like MS ;)

Sorry for wasting your time!