This can be manually triggered, however, by running %windir%\Microsoft.NET\Framework64\v9\ngen update. From what I can tell VS would usually queue up some kind of pre-build process which isn't triggered when the system isn't restarted.Installation must be "quiet" (since there's no GUI) and cannot request a restart.As such, I recommend using the images as a base. For some reason VS silently fails to copy some files when it detects some existing tools already being in place. I've had issues when installing VS on top of the images mentioned above.Generally, if you DON'T need (or some of the other tasks related to Visual Studio, like or the like) then you're better of using as your base and call it a day those images come with the Build Tools and VS Test agent already installed. I've recently spent a lot of time investigating this as our goal was to set up "dockerized" DevOps agents which were capable of running the pipeline task (among other things). So this seems to work! You should play with those -add installator arguments to specify what components you need precisely for your build, they correspond to workloads and components you see in the GUI. NET FrameworkĬopyright (C) Microsoft Corporation. Microsoft (R) Build Engine version 15.3.409.57025 for. (I'm pushing this image into lukaslansky/visualstudio-netwebworkload, use with caution.) RUN & 'C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/MSBuild/15.0/Bin/MSBuild.exe' /version RUN & "$env:TEMP\vs_community.exe" -add -quiet -wait -norestart -noUpdateInstaller | Out-Default RUN Invoke-WebRequest "" -OutFile "$env:TEMP\vs_community.exe" -UseBasicParsing
Let's try: FROM /windows/servercore:ltsc2019 Visual Studio seems to not be supported officially on Core Server, but I agree it would be really nice to be able to do this.
0 kommentar(er)
