-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Windows SDK 8.1 #842
Comments
@jamesmcguirepro , Could you please share the approximate size of this SDK? Also I see that Windows 8.1 SDK is officially deprecated in VS 2019.
|
@maxim-lobanov |
All SKUs of Windows 8.1 have left mainstream support. Only extended support is available for this version of Windows. You can install just the desktop/.NET SDK features (no tooling) via:
The SDK footprint is about 505MB, calculated from a clean machine install via:
|
Hi @jamesmcguirepro, considering that it can be installed on runtime and it's a pretty old version, we won't install it by default in the images. Thanks for the suggestion though. |
So IIUC the steps for getting Windows SDK 8.1 on windows-latest would be to:
|
@abergmeier Yep, specifically this should do:
|
because I did not bother to copy |
The following also works for me:
|
If you use PowerShell Core, you'll run into questionable semantics around HTTP 3xx status codes (see PowerShell/PowerShell#4534), hence the |
NB: MS SDK 8.1 is the default SDK you get when you install Visual Studio 2015 SP3 (even on a Windows 10 machine), and VS2015 itself is supported until 2025. So maybe there is an argument for providing it until VS2015 goes out of support? Or at least providing an action to install it when needed. The powershell example above works, but after a quick download it takes several minutes to install. Does anyone have an action or workflow recipe for caching the actual installation (or even know if that's possible - not sure if there are registry aspects needed in addition to the files themselves)? |
You can also install the SDK using an older version of vs_buildtools.exe. This is handy if you also need to install an older version of MSVC. In this example, I use v15 of vs_buildtools.exe to install platform tools v140 (VS 2015) and the windows 8.1 SDK. - name: Install MSVC 2015 (v140) and Windows 8.1 SDK
shell: powershell
run: |
$VS_BTOOLS_EXE="vs_buildtools.exe"
$VS_BTOOLS_URI="https://aka.ms/vs/15/release/vs_buildtools.exe"
Invoke-WebRequest -Uri $VS_BTOOLS_URI -OutFile $VS_BTOOLS_EXE
Start-Process -FilePath ./vs_BuildTools.exe -ArgumentList `
"--add", "Microsoft.VisualStudio.Component.VC.140", `
"--add", "Microsoft.VisualStudio.Component.Windows81SDK", `
"--quiet", "--norestart", "--force", "--wait" -Wait -PassThru (I based the example on this StackOverflow answer) |
Tool information
Area for Triage:
Question, Bug, or Feature?:
Virtual environments affected
Can this tool be installed during the build?
Possibly, with admin rights and a restart.
Tool installation time in runtime
Are you willing to submit a PR?
Yes. It existed before: https://github.com/actions/virtual-environments/blob/master/images/win/scripts/Installers/Windows2016/Install-VS2017.ps1#L61
The text was updated successfully, but these errors were encountered: