Framework 4.6.2 project failing to build using optimised instrumentation mode

I upgraded to NCrunch version 4.1 today (I was previously using version 3.31). When I use the default instrumentation mode (i.e. legacy) in my solution with 31 projects targeting .NET Framework 4.6.2 the NCrunch Tests window says it is monitoring 7,826 tests and the Risk/Progress bar is green and says "OK". Just as it did before I upgraded.

However, when I switch the instrumentation mode to optimised, the NCrunch Tests window shows it loading all 31 projects and starts to tell me that tests are queued for execution, but then says "1 project is failing to build" and does not identify which project it is having trouble with. The Risk/Progress bar says "Build".

[img=https://user-images.githubusercontent.com/2691303/68861384-5b75a180-06e3-11ea-9c21-a116c81670e2.png]NCrunch Tests and Risk/Progress Windows[/img]

I am running NCrunch inside Visual Studio Enterprise 2017 Version 15.9.17.

I have submitted a bug report from within Visual Studio with the same message and title to this post.

Hello,

Try installing the preview 4.2 builds from this post, that fixed it for my full-fat Framework solutions that exhibited the same error.

Regards;
Richard Moss

I'm afraid that didn't work, I still see 1 project failing to build when running NCrunch for Visual Studio 2017 version 4.2.0.1 in optimised instrumentation mode.

rdavis wrote:I'm afraid that didn't work, I still see 1 project failing to build when running NCrunch for Visual Studio 2017 version 4.2.0.1 in optimised instrumentation mode.

Thanks for confirming this.

I've taken a look at the bug report you've sent through, and it looks like you're experiencing a problem with the new optimised mode that hasn't been reported yet.

Something about this project results in NCrunch trying to resolve v0.0.0.0 of mscorlib. I'm not really sure how that's possible.

Can you tell me a bit more about this project? Which platform is it targeting, and which compiler is it using? Is there any post-build processing of the assembly? (i.e. IL weavers, postsharp, other manipulators).

Remco wrote:Thanks for confirming this.

I've taken a look at the bug report you've sent through, and it looks like you're experiencing a problem with the new optimised mode that hasn't been reported yet.

Something about this project results in NCrunch trying to resolve v0.0.0.0 of mscorlib. I'm not really sure how that's possible.

Can you tell me a bit more about this project? Which platform is it targeting, and which compiler is it using? Is there any post-build processing of the assembly? (i.e. IL weavers, postsharp, other manipulators).

Thank you for your reply.

The project has been in development for about 7 years, starting life in Visual Studio 2012 as a REST API using ServiceStack and MongoDB, the tests were written using NUnit and Moq.

Over the years it's grown and changed. It now has multiple website and API projects with references to SQL, AWS, NHibernate, xUnit.net, AutoFixture, NSubstitute, Dapper, and many more (but nothing that I can think of as being particularly out in left field).

It currently targets .NET Framework 4.6.2, is developed in Visual Studio 2017 and is deployed to 64-bit Windows Server 2016 running IIS 10 hosted by AWS. NCrunch is running on the same machine the software is developed on, 64-bit Windows 10 Pro computers. It is compiled using the Visual Studio IDE using the Debug configuration and the 'Any CPU' platform target.

I'm not aware of anything that would be doing post-build processing (we're not using any of the manipulators you listed). The only reference to a PostBuildEvent I can find in the csproj files is one instance of this:

  <PropertyGroup>
    <RunPostBuildEvent>OnOutputUpdated</RunPostBuildEvent>
  </PropertyGroup>

I cannot find any explicit references to mscorlib in any of the csproj files.

Thanks for these extra details. I'm working on a speculative fix for this and will let you know as soon as a build is available.

Could you try the build below and let me know if this resolves the issue?

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

Thank you, and apologies for the delay in replying.

I have now run the speculative fix (version 4.2.0.2) and all my tests are running, the risk bar is green and says OK, and the tests window says NCrunch is monitoring 7,921 tests (I've written more tests since I first posted!)