Do not pass -sign when building VisualFSharp.sln and FSharp.sln with .NET Core MSBuild on Windows

[ellahathaway]

When -sign is passed to build.cmd, building VisualFSharp.sln and FSharp.sln with .NET Core on Windows fails due to an empty ItemsToSign list. This is expected because artifacts are only produced when building the solution with the full framework MSBuild. This issue occurs regardless of whether -noVisualStudio is passed or not.

Rather than allowing the build to fail in this instance, we should consider adjusting the build script to avoid passing -sign in this scenario. Specifically, when building VisualFSharp.sln with .NET Core MSBuild, we should not set sign to true.

[ellahathaway]

If there are no artifacts to sign when building these solutions with .NET Core MSBuild, should we be building these solutions in this scenario? @dotnet/fsharp-team-msft

[T-Gro]

@KevinRansom : Kevin, would you know if we should be building it like Ella described?

[ellahathaway]

@T-Gro - I haven't been able to get a response from Kevin. I think he might be OOF? Is someone else on your team able to help?