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

Notification

Icon
Error
Cannot build on Grid Node with dotnet core 3.1 project
Options
Previous Topic Next Topic
shellicar
#1 Posted : Wednesday, February 19, 2020 3:45:53 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 5/25/2018(UTC)
Posts: 7
Location: Australia

Thanks: 1 times
Was thanked: 2 time(s) in 2 post(s)
Unsure as to why this doesn't work.

I have installed dotnet core SDK 3.1 on the server, confirmed that I can build using both Visual Studio 2019 and via the command line.
Ensured that there are no global.json files.
At first it was using the previous 2.x SDKs to build, no matter what.
The error would indicate that due to this SDK being used, it doesn't support 3.1.
After uninstalling all dotnet core 2.x SDKs from the machine, this is the error reported.

Code:

NCrunch: This project was built on server 'dev-01'
Project.csproj (0, 0): The target "Build" does not exist in the project.
Back to top
Remco
#2 Posted : Wednesday, February 19, 2020 10:27:58 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 932 times
Was thanked: 1258 time(s) in 1171 post(s)
Hi, thanks for sharing this issue.

The error that you are receiving is caused by the primary build target referenced by the .proj file not being present in its expected location. Probably, the issue here is some kind of inconsistency in the toolset being used between the grid node server and your local client machine.

Check that the grid node is running the exact same version of VS as the client machine, and that the projects are specifically written to target the version of .NET Core you're trying to use. It may be worth examining the project file in the generated NCrunch workspace on the remote grid node to see if it can yield any clues about why the version of .NET Core being resolved is the wrong one. Generally, if a command-line MSBuild of the generated project file in the workspace fails, then NCrunch will fail in the same manner.

Note that the installation of .NET core is not as simple as it might seem. There are connections between .NET core version resolution and the version of VS that is installed. There are also different install paths for .NET Core dependent on target platform (x64/x86). Where possible, I would suggest setting up your grid nodes to be as similar to your client machines as possible in terms of installation structure and SDKs ... this generally helps to avoid weird issues. There are a lot of moving parts in the MS platform.
Back to top
shellicar
#3 Posted : Tuesday, March 24, 2020 1:55:54 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 5/25/2018(UTC)
Posts: 7
Location: Australia

Thanks: 1 times
Was thanked: 2 time(s) in 2 post(s)
Thanks for the response, sorry for taking so long to reply.

As mentioned the project built using Visual Studio, and the command line (dotnet.exe)
Both x64 and x86 dotnet SDKs were installed.

However the issue did resolve itself after updating Visual Studio 2019, I'm unsure of the exact before and after versions however.
Back to top
1 user thanked shellicar for this useful post.
Remco on 3/24/2020(UTC)
Users browsing this topic
Guest
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.035 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download