Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Build Environment   (RSS)

Installing Win SDK for Svr 2008 after VS 2008 breaks VS command line build environment

Issue : After installing the Windows SDK for Server 2008, you are no longer able to build at the VS2008 command line. You receive an error that csc, vbc, and/or msbuild commands are not recognized. You are able to build without problems in the VS IDE.

Workaround: SDK build env fails on X86 XP with VS2005

This article applies to the Windows SDK for Windows Server 2008 and .NET Framework 3.5 . Problem: If your usage scenario matches the one listed below , you will be unable to build in the Windows SDK command line build environment. If you type cl.exe in

Integrating Windows SDK and VS with new SDK Configuration tool

This article describes the use of the Windows SDK Configuration tool, which is included in the Windows SDK for Windows Server 2008 and .NET Framework 3.5 and works with Visual Studio 2005 and Visual Studio 2008, including Visual Studio 2008 Express SKUs.

SDK Workaround: Visual C++ cross-compilers fail on 64-bit platforms

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 On 64-bit platforms, the Visual

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

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

Updated Windows SDK Visual C++ Cross Compilers

During Windows SDK setup you are given the option to select VC++ compilers for every platform you wish to develop for. The Windows SDK for Server 2008 and .NET Framework 3.5 (available as a beta now) ships 5 new VC++ version 9 (Visual Studio 2008) compilers

SDK Workaround: Running Visual Studio 2005 Integration 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".

SDK Workaround: VCBuild fails to compile or upgrade projects

This workaround applies to: · The prerelease Windows SDK for Windows Server 2008 and .Net Framework 3.5 (RC0) In order for VCBuild to run properly, vcprojectengine.dll needs to be registered. If vcprojectengine.dll is not registered, VCBuild.exe will

SDK Workaround: .Net Framework 3.5 is not in the Windows SDK path

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 .Net Framework 3.5 is not

SDK Workaround: After Visual Studio integration, extra paths are added to the VC++ Directories

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 After running Visual Studio
 
Page view tracker