create visualstudio2017-workload-manageddesktopbuildtools

[jberezanski]

No description provided.

[pstephenson02]

Hi @jberezanski

I have a Dockerfile that currently installs some of the vsbuildtools:

RUN choco install visualstudio2017buildtools -y
RUN choco install visualstudio2017-workload-webbuildtools -y
RUN choco install visualstudio2017-workload-netcorebuildtools -y

However, I also need the Microsoft.VisualStudio.Component.FSharp.MSBuild component in the Microsoft.VisualStudio.Workload.ManagedDesktopBuildTools workload. I tried modifying my script by adding:

RUN choco install visualstudio2017buildtools --package-parameters "--add Microsoft.VisualStudio.Component.FSharp.MSBuild" -y

But the build fails as it's unable to find the componenet:

Failures
 - Microsoft.VisualStudio.Component.FSharp.MSBuild - Microsoft.VisualStudio.Component.FSharp.MSBuild not installed. The package was not found with the source(s) listed.

Since this workload does not exist yet (hence this Github issue), is there any way that I can work around this until this issue is complete? I'm working inside of a Docker container with Windows Server Core so I cannot open the visual studio installer and add workloads that way. Is there a programmatic way to do this?

Thanks in advance.

[jberezanski]

Oh, @pstephenson02, somehow I completely missed your comment.

The syntax

choco install visualstudio2017buildtools --package-parameters "--add Microsoft.VisualStudio.Component.FSharp.MSBuild" -y

is correct and should work in cmd/powershell. The fact that it fails in a dockerfile suggests a quoting issue - it looks like docker strips the quotes from the command, so choco thinks that Microsoft.VisualStudio.Component.FSharp.MSBuild is the name of another package to install, not a continuation of the value of --package-parameters.

The workload package is available now, so you can just use it and avoid the issue. You can also try to determine how to escape the quotes properly in the dockerfile, which may come in handy if you need to pass additional parameters to the packages in the future.

[pstephenson02]

Thanks @jberezanski!