Build managed tests with dotnet

[chsienki]

Similar to the way we now build the xunit wrappers with the CLI dotnet, this change moves the managed projects to use the CLI as the build invoker as well.

On the build servers we only have the 1.1 sdk installed, which leads to failures in the tests when building them using desktop msbuild. While we could install a newer sdk on the build machines, and most developers already have a suitable > 2.0 sdk, this reduces our external dependencies and ensures the builds won't fail due to external environment issues.

[AaronRobinsonMSFT]

Is this property still used in SDK projects? I always thought of this as a very VS specific property.

[chsienki]

Yes, it's still used. By default in SDK projects it seems to be set to x64/x86 etc, rather than AnyCPU. For the cross arm builds, we build the test exes on windows and copy them to arm, so compiling not AnyCPU breaks that.

[sbomer]

Why are we no longer passing the Priority argument? And do we need to pass TargetsWindowsMsbuildArg?

[chsienki]

And this is why I asked for a review 👍 Let me take a look

[4creators]

Call in this form misses on default parameters passed by run.cmd to msbuild call. One of them already missed in TestWrapper builds is /clp:Summary which prints summary of run. All default parameters are available in config.json in repo root.

[4creators]

Pls restore default parameters

[4creators]

Thanks

[BruceForstall]

This has broken pri-1 builds, e.g.:

16:37:14 BUILDTEST: Starting the Managed Tests Build
16:37:14 BUILDTEST: Building tests group 2 with 16 subgroups
16:37:14 
MSBUILD : error MSB1001: Unknown switch.
16:37:14 Switch: -priority=1
16:37:14 
16:37:14 For switch syntax, type "MSBuild /help"

https://ci.dot.net/job/dotnet_coreclr/job/master/view/x64/job/checked_windows_nt/10074/consoleFull#-208510365679494335-f7bd-47d0-8771-8661e00c2db2

I'm going to revert it.