The partial download issue is probably: PowerShell/PowerShell#17931, which was fixed in PowerShell v7.4.0.

Nevertheless, eng/AcquireWasiSdk.targets appears to employ Windows PowerShell, which was released in 2016.

Should we first check whether curl is available, it was only added in Windows build 17063.

.NET 10.0 - Supported OS versions indicates we still support all the way back to Windows Server 2012 (build 9200).

Should we first check whether curl is available, it was only added in Windows build 17063.

Let's see. I would hope the CI build machines that are used for WASI are new enough.

Should we first check whether curl is available, it was only added in Windows build 17063.

Let's see. I would hope the CI build machines that are used for WASI are new enough.

If this only runs on CI and not locally, then that’s not an issue. In that case, you could have probably used pwsh instead of powershell to use the maintained PowerShell instead of legacy Windows PowerShell.

If this only runs on CI and not locally, then that’s not an issue

It runs when you try to build some WASI-related component (mostly native code). There are not that many people interested in building dotnet/runtime targeting WASI on Windows. I suspect none of them are running particularly old OS versions. If that turns out to be an incorrect assumption, we can augment the code then.

It runs when you try to build some WASI-related component (mostly native code). There are not that many people interested in building dotnet/runtime targeting WASI on Windows.

For future reference, the curl implementation could be made conditional on:

[Environment]::OSVersion.Version.Build -ge 17063

otherwise fallback to Invoke-WebRequest.

It worked just fine :)

edit: I made it silent

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.