switch to Bullseye and SimpleExec

[adamralph]

• Bullseye replaces simple-targets-csx (it's a regular binary package instead of scripts, so can optionally be used in a regular .NET project).
• SimpleExec wraps up command invocation, so removes the need to include local helpers

[adamralph]

I think the build is failing for an unrelated reason.

[mauroservienti]

thanks @adamralph ! I'll have a look at the build server error to understand what's going on.

[adamralph]

FYI I amended the commits to use Bullseye.1.0.0-rc.4 and SimpleExec.2.2.0 (using netstandard2.0).

[adamralph]

@mauroservienti @nazarenomanco the last commit broke the script. When the versions of packages are updated, the corresponding paths in the scripts need to be changed:

• Radical/src/build.cmd

  Line 9 in f2f4773

  set CSI_VERSION=2.3.2

• Radical/src/build.csx

  Line 1 in f2f4773

  #r "packages/Bullseye.1.0.0-rc.5/lib/netstandard2.0/Bullseye.dll"

• Radical/src/build.csx

  Line 2 in f2f4773

  #r "packages/SimpleExec.2.2.0/lib/netstandard2.0/SimpleExec.dll"

• Radical/src/build.csx

  Line 8 in f2f4773

  var vswhere = "packages/vswhere.2.1.4/tools/vswhere.exe";

I wondered why the CI build didn't fail, but that's because you are not using the build script in appveyor.yml. I recommend switching appveyor.yml to use the build script, so that the same process is used both locally and in CI, and your CI will guarantee that the build script works.

Also, you may want to consider switching to a regular C# project instead of a script. That will remove the need to use Microsoft.Net.Compilers and you can upgrade to newer versions of Bullseye and SimpleExec by editing the csproj only. And if you can switch to using dotnet instead of msbuild then you can remove the need to use vswhere.