Question: Is .NET CLI or VS 2017 supported?

[conniey]

Hi,

I am trying to update our repository to VS1017, but the build.ps1 uses dotnet.exe and msbuild 15 because we are building a VS2017 extension. Is the .NET Core CLI 1.0.0 or msbuild 15 supported? It doesn't appear to be under the Onboarding Steps, and the PR is failing because it can't locate dotnet.exe in its path.

Thanks!

[mmitche]

@conniey dotnet.exe will not be on the path on any of the machines. There are simply too many versions laying around to risk putting it on the path. That said, a machine with VS2017 is available, which should put dotnet.exe on the path if you run the vs developer prompt inside your CI script.

https://github.com/dotnet/dotnet-ci/blob/master/jobs/generation/Utilities.groovy#L239

Let me know if you need help.

[conniey]

Thanks!

[conniey]

@mmitche, I was checking out my CI build and it appears to be unable to locate Visual Studio 2017. Could I be missing something?

• dotnet-apiport PR 411
  • Script/line it is failing on: Set-VsDevEnv.ps1 #L45
  • netci.groovy
• CI console output

Error:

11:54:00 D:\j\workspace\Debug_prtestf8d899aa\build\Set-VsDevEnv.ps1 : Could not locate: C:\Program Files (x86)\Microsoft Visual Studio\2017. 

[mmitche]

@conniey You need to commit the change to the netci.groovy before the PR changes will be visible.

[conniey]

@mmitche Hey, I did that and then put my commits on top of it.. but I am getting the same issue. :/ Is there any way to see what's on the machine building the PR?