Troubleshooting Windows SDK Sample Building on X64

Are you having problems building some of the Windows Vista SDK samples on an X64 machine? Me too. That’s why I’ve posted a series of workarounds on the Windows SDK Blog for the errors I see popping up most often. Lots of these issues will get better in the upcoming Windows SDK for Windows Server 2008 and .NET Framework 3.5.

Have you found workarounds to other issues? Share them here or email me. I’m the Samples PM for the Windows SDK Team and want to know what you love and hate about samples in the Windows SDKs.

Troubleshooting sample building issues on X64, post 1 covers an error that affects everyone building managed samples with the .NET Framework: SetEnv.cmd uses X86 framework

Troubleshooting sample building issues on X64, post 2 covers (Managed) error MSB3011: "C:\Windows\Microsoft.NET\Framework\v2.0.50727\AL.exe" was not found. Either 1) Install the .NET Framework SDK, which will install AL.exe. Or 2) Pass the correct location of AL.exe into the "ToolPath" parameter of the AL task.

Troubleshooting sample building issues on X64, post 3 covers vcbuild.exe : warning VCBLD6001: Project 'c:\samples2003X64DEBUG\Sample\Foo.vcproj' does not support platform 'x64', or the platform support DLL for this platform is not installed.

Troubleshooting sample building issues on X64, post 4 covers Error :   Msbuild Reports a Dependency upon the Microsoft .NET Framework SDK 2.0.

Troubleshooting sample building issues on X64, post 5 covers Error :   link fails with "fatal error LNK1181: cannot open input file”

Troubleshooting sample building issues on X64, post 6 covers Error:   C:\Sample\Foo.csproj(57,11): error MSB4019: The imported project "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Microsoft.CompactFramework.CSharp.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.

Troubleshooting sample building issues on X64, post 7 covers Error: Linking....\Release\Foo.obj : fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'X86'