Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
2 Pages<12
ASP.NET Core 2.1 integration tests
Options
Previous Topic Next Topic
Remco
#21 Posted : Wednesday, September 4, 2019 12:09:02 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,976

Thanks: 931 times
Was thanked: 1257 time(s) in 1170 post(s)
Hi, thanks for sharing this problem.

This looks like a dependency collocation issue. Could you try turning on the 'Copy referenced assemblies to workspace' NCrunch project-level configuration setting for all the projects involved? Does this solve the issue?
Back to top
gasiino
#22 Posted : Wednesday, September 4, 2019 9:01:23 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 9/3/2019(UTC)
Posts: 3
Location: United Kingdom
Hi, thanks for your answer.

I have just tried that and it doesn't cause any changes.
It seems like NCrunch is looking for the json file regardless of the presence of the dlls in the folder.
If there is a solution, that would be great.

However, I am wondering if this is something that is already fixed in following versions of dotnet. If that's the case, we might switch to a newer version in a few months time.
Is the problem solved in more recent frameworks of dotnet?
Is this a problem that is caused to a msbuild error? (I understand one of the targets is picking on the wrong folder).
Back to top
Remco
#23 Posted : Wednesday, September 4, 2019 11:43:59 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,976

Thanks: 931 times
Was thanked: 1257 time(s) in 1170 post(s)
Provided you're using .NET Core 2.2 or above, then there shouldn't be a known issue with these tests. However, the architecture of this library and the manner of its development has made it hard for us to integrate with it, so it wouldn't surprise me if there is an unconsidered edge case or a version that has changed from the known state.

The code trying to resolve the .json file isn't actually NCrunch - it'll be something in the .NET runtime or associated libraries. Normally this file should be present inside the build output directory of your test project if the 'Copy referenced assemblies to workspace' is turned on.

Is there any chance you can reproduce this problem with a small self contained sample solution? If you can share such a solution with me via the contact form, I'll be happy to take a closer look and provide further advice or a fix.
Back to top
gasiino
#24 Posted : Wednesday, September 4, 2019 12:10:45 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 9/3/2019(UTC)
Posts: 3
Location: United Kingdom
Hi,
thanks for your answer.

We are targetting net462, not dotnetcore yet.

I was looking for confirmation that this issue should disappear as soon as we migrate into dotnetcore 3.0, which we plan to do.

Thanks
Back to top
Remco
#25 Posted : Thursday, September 5, 2019 1:23:22 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,976

Thanks: 931 times
Was thanked: 1257 time(s) in 1170 post(s)
It's impossible for me to confirm this 100% without being able to reproduce and analyse the issue, but I'd say there is a better than even chance that upgrading to .NET 3.0 will resolve the issue.

Certainly if it doesn't, I will do my best to help resolve it :)
Back to top
Users browsing this topic
Guest
2 Pages<12
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.041 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download