Menu
I'm setting up my first build server for .NET 3.5 projects, and found this interesting line in the MSBuild log after a successful build of a simple test application:
Could not locate the expected version of the Microsoft Windows SDK. Looked for a location specified in the "InstallationFolder" value of the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v6.0A". If your build process does not need the SDK then this can be ignored.
When exactly would your build process need the SDK? I don't want to install it on the build server if it's not going to be necessary, but I also don't want to discover that I need it by having a build mysteriously break.
At the moment, I only have .NET Framework 3.5 SP1 installed on the server.
234
The Windows App SDK provides a unified set of APIs and tools that are decoupled from the OS and released to developers via NuGet packages. These APIs and tools can be used in a consistent way by any desktop app on Windows 11 and downlevel to Windows 10, version 1809.
The windows SDK is necessary if you intend to develop windows applications (with GUI, low-level graphics, windows filesystem specific I/O, tweaking registry settings, developing windows services or device drivers, etc etc).
Visual StudioYou must have the Windows 10 SDK installed, version 10.0. 15063 or later.
MSBuild versions with Visual Studio, but is also included in the . NET SDK. The SDK has a minimum version of MSBuild and Visual Studio that it works with, and it won't load in a version of Visual Studio that's older than that minimum version.
The SDK has a couple of additional tools that are **sometimes** used, depending on the contents of your project - such as (IIRC) the reports compiler. But for most things, no: you don't need the SDK. I installed in on my build server just to get clean output ;-p
64
If you need to compile C or C++ code - to the best of my knowledge.
40
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
