.Net Core 3.1 with WPF classes fail - NCrunch Support Forum

jotto

#14235 6 years ago 18 Dec 2019 11:25 UTC

I have recently converted a project from .Net Framework 4.8 to .Net Core 3.1. The tested classes are using BitmapSource from WPF.

When I try to run these tests, I'm getting the following exception:

System.IO.FileNotFoundException : Could not load file or assembly 'PresentationCore, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. The system cannot find the file specified.

It seems like NCrunch doesn't resolve the WPF dependency somehow.

The test project file looks like this:

[h]<PropertyGroup>
<TargetFramework>netcoreapp3.1</TargetFramework>
<IsPackable>false</IsPackable>
...
<UseWPF>true</UseWPF>
</PropertyGroup>
[/h]

Is this an NCrunch bug, or is there something I haven't configured properly?

Edited 6 years ago 18 Dec 2019 11:26 UTC

Hunter-d-_-b

#14236 6 years ago 18 Dec 2019 16:11 UTC

I'm not an expert but I had a similar issue recently with my solution.

In NCrunch
Go to: Configuration > Build Settings > Copy referenced assemblies to workspace = True

Let me know if it worked for you :)

Remco NCrunch Developer

#14239 6 years ago 18 Dec 2019 23:29 UTC

It's possible that this is a v4.2 regression - https://forum.ncrunch.net/yaf_postst2892_Could-not-load-file-or-assembly-after-4-2-0-7-update.aspx.

We're investigating this. I recommend trying the 'Copy referenced assemblies to workspace' setting (as suggested above), or rolling back to v4.1 to see if that fixes it.

jotto

#14242 6 years ago 19 Dec 2019 08:20 UTC

Thanks for following up guys. Unfortunately I'm getting the same error with "Copy referenced assemblies to workspace".

Remco NCrunch Developer

#14245 6 years ago 19 Dec 2019 12:10 UTC

jotto wrote:Thanks for following up guys. Unfortunately I'm getting the same error with "Copy referenced assemblies to workspace".

Thanks for confirming this. Right now I believe it to be caused by this problem: https://forum.ncrunch.net/yaf_postst2892_Could-not-load-file-or-assembly-after-4-2-0-7-update.aspx

I recommend following the above thread for updates on the issue. Sadly, it's a tough one that might take us a while to crack. If you have the option, I recommend keeping your setup on an older toolset a little longer so you can still use NCrunch until we can fix the problem.

michaelkroes

#14259 6 years ago 20 Dec 2019 20:39 UTC

jotto

#14264 6 years ago 21 Dec 2019 09:33 UTC

It still fails. Fortunately it's easy to reproduce with a test :-)

[h]using System.Windows.Media;
using System.Windows.Media.Imaging;
using NUnit.Framework;

namespace MyNamespace
{
[TestFixture]
public class FailingTestClass
{
[Test]
public void FailingTest()
{
var bitmapSource =
BitmapSource.Create(10, 10, 96, 96, PixelFormats.Bgra32, null, new byte[10 * 10 * 4], 10 * 4);
}
}
}[/h]

michaelkroes

#14265 6 years ago 21 Dec 2019 13:00 UTC

Thanks!

I've got it reproduced and I will get back to you.

michaelkroes

#14266 6 years ago 22 Dec 2019 11:47 UTC

jotto

#14267 6 years ago 22 Dec 2019 12:02 UTC

Do you guys never take a break during weekends? :-D

Thanks -- it works now!

michaelkroes

#14268 6 years ago 22 Dec 2019 14:33 UTC

Thanks for the quick confirmation!

Post a reply