SDK Workaround: MSBuild Reports Dependency on .NET Framework SDK 2.0

  • Article

This workaround applies to:

 

·         The prerelease Windows SDK for Windows Server 2008 and .Net Framework 3.5 (RC0), September, 2007

·         The prerelease Windows SDK for Windows Server 2008 and .Net Framework 3.5 (IDS04), July, 2007

·         The Windows SDK Update for Windows Vista (RTM), March, 2007

 

The Windows SDK does not set the HKLM\Software\Microsoft\.NETFramework\sdkInstallRootv2.0 registry key to a string value containing the root directory of the Windows SDK installation. Some MSBuild tasks may expect this registry key to be set. If you already have the .NET Framework SDK 2.0 or Visual Studio 2005, this key will be set and you should not encounter a problem. However, if you install the Windows SDK without either the .NET Framework SDK or Visual Studio 2005, you may receive an error message from MSBuild tasks with a dependency on this key. To work around this issue set the string value of this key to the root directory of the Windows SDK installation. By default, this is: C:\Program Files\Microsoft SDKs\Windows\v6.1 (v6.0 on the Vista Update SDK)

 

Additionally, in order to use AL.exe, the ALToolPath parameter must be set and passed to msbuild. For the default install location, this can be done using the following command:

msbuild /p:ALToolPath="C:\Program Files\Microsoft SDKs\Windows\v6.1\Bin