Geek Answers Handbook

When do you need the Windows SDK for MSBuild?

I am setting up my first build server for .NET 3.5 projects and found this interesting line in the MSBuild log after successfully building a simple test application:

Could not find the expected version of the Microsoft Windows SDK. I looked for the location indicated in the "InstallationFolder" value by the registry key "HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Microsoft SDK \ Windows \ v6.0A". If your build process does not require an SDK, then this can be ignored.

When exactly should your build process have an SDK? I do not want to install it on the build server if it is not necessary, but I also do not want to discover that I need it, creating a mysterious gap.

At the moment, only the .NET Framework 3.5 SP1 is installed on my server.

+5
source share
2 answers

There are several additional tools in the SDK that ** are sometimes used ** depending on the contents of your project, for example (IIRC), a report compiler. But for most things not: you don't need an SDK. I installed builds on my server only to get clean output; -p

+3
source

If you need to compile C or C ++ code, as far as I know.

+1
source

More articles:


All Articles