VS2022 with Net 6 sln, keeping it simple just a Class Library.

Builds fine and nCrunch runs tests locally no issue.

Set up a grid node, installed Net 6 SDK.
GridNode wouldn't build with error:
NCrunch was unable to parse this project file because of an unexpected error: Microsoft.Build.Exceptions.InvalidProjectFileException: The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the <Project> element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.

Install MsBuild via 2022 Installer -> Individual Components
GridNode won't build with error:
The target "Build" does not exist in the project.

Builds fine from the command line "dotnet restore && dotnet msbuild" from a local CMD prompt.

Following relevant advice gleaned from forum running the GridNode in a console host to produce:
Now initialising NCrunch Grid Node using console host. Version is 4.11.0.2
Grid node successfully started and is listening for connections on port 41141
[PID:10740 21:06:15.2081 ?-1] Node server started - listening on port 41141
[PID:10740 21:08:55.2551 Core-13] Client connection accepted from 192.168.xxx.126:50264
[PID:10740 21:08:55.2711 Core-13] Creating server-side handler for 192.168.xxx.126:50264
[PID:10740 21:08:55.2711 Core-13] Describing self to 192.168.xxx.126:50264
[PID:8176 21:13:01.8331 ?-10] The target "Build" does not exist in the project.
[PID:10740 21:13:02.1301 NodeProcessor-255] ERROR (Build): xxxNet: C:\NCrunch Grid Node\10740\1\xxxNet\xxxNet.csproj (0): The target "Build" does not exist
in the project.

Any suggestions what's missing?

Forgot to say FWIW I set nCrunch logging to detailed and the GridNode just returns one line "no build target" but if you'd like me to send the log from the successful local build let me know and I'll email.

dotnet --version
6.0.300

dotnet msbuild --version
Microsoft (R) Build Engine version 17.2.0+41abc5629 for .NET
Copyright (C) Microsoft Corporation. All rights reserved.

17.2.0.20702

Found another pointer and set DOTNET_MSBUILD_SDK_RESOLVER_CLI_DIR = "C:\Program Files\dotnet". No difference.

Simplifying further added new Class Library with default content; builds local, fails with same error on the node. Literally VS2022->Add new Class Library->Select NEt6
<Project Sdk="Microsoft.NET.Sdk">

<PropertyGroup>
<TargetFramework>net6.0</TargetFramework>
<ImplicitUsings>enable</ImplicitUsings>
<Nullable>enable</Nullable>
</PropertyGroup>

</Project>

with default Class1. Same "No build target" error.

Builds fine on the GridNode using the command lines "dotnet restore && dotnet msbuild" from a local CMD prompt.

It does not have a full Visual Studio install, only the MsBuild Individual Component. Just pointing msbuild at
the sln wasn't happy though, iirc something to do with Net461 which didn't make a whole lot of sense without further investigatingthe command line options. I'll tryagain this evening and post the result.

If you could suggest a commandline to use to give info you need let me know.

Ok, found and installed "Build Tools for Visual Studio 2022" from https://visualstudio.mic...ownloads/?q=build+tools

Even with that installed nCrunch comes back same error; but even msbuild (parameterless) while it works on Dev machine with full VS installed it still fails on the GridNode with mbs4236 & a global.json doesn't seem to help.

If you can offer any advice (even if it's no chance; you couldn't get it to work either fair) to get this working I'd gratefully receive as I really don't want to load a full VS if it can be avoided; but I appreciate this is more a MS issue than nCrunch... will revert with findings either way.

Lame but not wholly unanticipated outcome; I set up another node with a minimal for our needs full install of VS2022 with which nCrunch is happy.

ROI on VS Build Tools for 2022 with several evenings expended is 0. Even msbuild still doesn't work. YMMV; and please reopen/reply here if you do better.

For us:

• msbuild can't/doesn't/won't resolve the NetCore.Sdk.
  
• dotnet msbuild is happy as...
  

FWIW a prior workplace foisted a VS Enterprise licence upon me just so I could report back that for all that extra expense MsLiveUnitTest just doesn't come close.
A full [minimal] install of VS on the node is a small price to pay for orders of magnitude better experience.
Keep up the good work; and let us know when you overcome the "dotnet msbuild" incompatibilities.