Workaround: MSBuild and/or VCBuild fail to find Win 7 SDK headers, libs and tools

This post applies to the RC release of the Windows SDK for Windows 7 and .NET Framework 3.5 SP1. Scenario: if VS2008 or another Windows SDK is installed, MSBuild and/or VCBuild may default to the headers, libs and tools of the older SDK.   Samples or applications built in the SDK build environment or in Visual…

1

Using WinSDK, DirectX SDK and VS2008

It can be a bit tricky to use the DirectX SDK, the Windows SDK, and Visual Studio 2008.  If you’re building an application in the Windows SDK command line build environment or in Visual Studio2008 IDE, you should ensure that the DirectX SDK include, library, and executables directories are set correctly in Visual Studio 2008….

1

VC++ compilers in Windows 7 SDK

The newly released Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1: BETA is available on the Microsoft Download Center with updated VC++ compilers.  The Windows 7 SDK includes the Enterprise versions of the VS 2008 SP1 (v9.0) compilers and runtimes, which come from the Visual C++ team.  Compilers installed by default  Platform/Processor…

1

How to get the SDK Configuration Tool to work

The Windows SDK Configuration Tool sets which version of Windows SDK headers, libraries and tools you want to build with in Visual Studio. The tool shipped with the Windows SDK for Server 2008 but has had several problems. Here’s how to get it working in your scenario. Instructions are different depending on which Visual Studio…

1

How-to: In search of strmbase.lib

Several of the DirectShow samples in the Windows SDK require strmbase.lib, and quite a few developers have asked me where to find this file. It does not install to the default location with other libraries (C:\Program Files\Microsoft SDKs\Windows\v6.1\lib). Other folks have figured out how to build strmbasd.lib, but they need strmbase.lib. Strmbasd.lib is not included…

1

Pros and Cons of Shared Compilers in Win SDK and VS2008

  About the shared compilers in the Windows SDK The compiler installed with Windows SDK for Windows Server 2008 support vertical integration with the all other VS SKUs that install the compilers. (A ‘SKU’ or ‘Stock Keeping Unit’ is an identification assigned to an individual product.) Vertical integration means that a feature is shared among…

0

XCOPY the Windows SDK?

I’ve heard from a couple of developers lately that want to be able to XCOPY the Windows SDK, the .NET Framework SDK, and all of the tools. These users want the tools used to build their product to be checked into the source repository along with the code, so that the build tools can be…

1

Visual Debugger for MsBuild

Are you looking for a visual debugger for MsBuild? It seems like lots of folks are. Looking at the results of the  feature poll on the MSBuild blog, I see that a debugger for MSBuild projects is the number one vNext request from users.  Well, wait no more. Partho Das, a developer in Visual Studio…

1

Setting build environment to target Windows Vista Sp1

You can use the switches shown below to target different operating systems from within the SDK build environment.  To target Windows Vista you should use the /vista switch.  To target Windows Vista Sp1 (or Windows 2008) you should use the /2008 switch.  Launch the Windows SDK build environment (Start, All Programs, Microsoft Windows SDK, CMD…

1

SDK Workaround: VS 2005 Integration Tool fails on Vista

This workaround applies to:    ·         The prerelease Windows SDK for Windows Server 2008 and .Net Framework 3.5 (IDS04), July, 2007   In Windows Vista, running the Visual Studio 2005 Registration Tool fails with the error “Unable to access the required files”. This is because the integration tool needs to be run with elevated privileges: …

1