Windows SDK for Server 2008 (v6.1) overwrites VS2008 SP1 CRT files

Issue: If you install the Windows SDK for Windows Server 2008 and .NET Framework 3.5, on top of any post-RTM Visual Studio update (such as a Service Pack or Feature Pack), some CRT  files will be reverted  back to RTM version.  Cause: This problem occurs when you install the Windows SDK for Windows Server 2008…

1

Win 7 SDK (RC) can disable x64 config platform choices in VS2008 RTM.

Installing the Windows 7 SDK (RC release) and Visual Studio 2008 RTM can disable the X64 and Itanium configuration platform choices in Visual Studio. If the Windows 7 SDK (RC release) and Visual Studio 2008 RTM are installed on a machine running an x64 version of Windows the following issue may occur. The Itanium and…

1

Win SDK for Server 2008 plus VS2008 causes double X64 platforms in VC Directories

Issue: Installing the Windows SDK for Windows Server 2008 after Visual Studio 2008 Standard on a computer with an X64 operating system corrupts VC directories, causing a double X64 entry.  This post applies to the Windows SDK for Server 2008 only.  This issue has been fixed in subsequent SDKs. Scenario: You probably have this issue…

0

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

What's the difference between "CLR" and ".NET Framework"?

What’s the difference between "Common Language Runtime (CLR)" and "Microsoft .NET Framework"?  David Broman’s post explains it beautifully and was very helpful to me. CLR + managed libraries and tools = Microsoft .NET Framework The CLR is the low-level technology (much of it written in unmanaged, native code) that includes the garbage collector, security subsystem,…

1

What WinSDK files changed in VS2008 SP1?

 Wondering what changed in the WinSDK components that ship in Visual Studio between VS2008 RTM and VS2008 SP1?  Chris Hubbard, an SDET on the Windows SDK team, has posted a list of new files in VS 2008 SP1 and also the files that have changed.  See WinSDK in VS2008 SP1: what changed?  For starters,  only…

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

Windows SDK components missing from VS 2008?

A couple of developers have written asking why the Windows SDK components that were expected to install with Visual Studio 2008 were missing after Visual Studio installed.  The Windows SDK installs several version 6.0a components whenever Visual Studio is installed: Windows headers are installed by default to \Program Files\Microsoft SDKs\Windows\v6.0A\include Windows libraries are installed by…

2

Workaround: VS2008 SP1 Breaks WinSDK Configuration Tool

Issue: Installing Visual Studio 2008 SP1 breaks the Windows SDK Configuration tool in the Windows SDK for Windows Server 2008 and .NET Framework 3.5.  This tool is used to set the version of Windows SDK headers, libraries and tools you wish to build with in Visual Studio.  After installing VS 2008 SP1, the Configuration tool…

1