Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Build fails due to missing RoslynTools.MSBuild 16.0.0-alpha

See original GitHub issue

@ArrowCase commented on Sun Mar 24 2019

I wasn’t sure whether this issue belongs here or in dotnet/arcade. Please feel free to move it.

Steps to reproduce: Clone repository, run build.cmd.

Results:

dotnet-install: Downloading link: https://dotnetcli.azureedge.net/dotnet/Sdk/3.0.100-preview3-010436/dotnet-sdk-3.0.100-preview3-010436-win-x64.zip
dotnet-install: Extracting zip from https://dotnetcli.azureedge.net/dotnet/Sdk/3.0.100-preview3-010436/dotnet-sdk-3.0.100-preview3-010436-win-x64.zip
dotnet-install: Adding to current process PATH: "C:\Users\user\source\repos\winforms\.dotnet\". Note: This change will not be visible if PowerShell was run as a child process.
dotnet-install: Installation finished
Downloading vswhere
Downloading RoslynTools.MSBuild 16.0.0-alpha
No package matching package identifier RoslynTools.MSBuild and version 16.0.0-alpha was found in the given feed.

Version 16.0.0-alpha of the package indeed does not appear to exist, but 16.0.0-rc1-alpha does.

Additionally, running build a second time results in a different error:

Exception calling "Start" with "0" argument(s): "The system cannot find the file specified"
System.Management.Automation.MethodInvocationException: Exception calling "Start" with "0" argument(s): "The system cannot find the file specified" ---> System.ComponentModel.Win32Exception: The system cannot find the file specified
   at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
   at CallSite.Target(Closure , CallSite , Object )
   --- End of inner exception stack trace ---
   at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)
   at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
at Exec-Process, C:\Users\user\source\repos\winforms\eng\common\tools.ps1: line 69
at MSBuild, C:\Users\user\source\repos\winforms\eng\common\tools.ps1: line 476
at InitializeToolset, C:\Users\user\source\repos\winforms\eng\common\tools.ps1: line 422
at Build, C:\Users\user\source\repos\winforms\eng\common\Build.ps1: line 76
at <ScriptBlock>, C:\Users\user\source\repos\winforms\eng\common\Build.ps1: line 125
at <ScriptBlock>, <No file>: line 1

@zsd4yr commented on Wed Mar 27 2019

@OliaG @merriemcgaw would one of you kindly move this to dotnet/arcade ?

Issue Analytics

State:
Created 4 years ago
Comments:9 (9 by maintainers)

Top GitHub Comments

1reaction

tmatcommented, Apr 1, 2019

Since the non-numeric part of the version changed, these scripts can no longer make an educated guess about the best package to pick.

Exactly, because the script doesn’t know to append “rc1”. It only knows what VS version the repo needs (e.g. “15.9”, “16.0”).

I don’t think we need to change anything. The default will work once we create “16.0.0-alpha” package and if anyone needs anything else they can specify it explicitly. I’ll update doc - it doesn’t mention xcopy msbuild.

0reactions

tmatcommented, Apr 2, 2019

Added a doc: https://github.com/dotnet/arcade/pull/2401