Workaround: VCBuild fails to compile or upgrade projects in SDK
There is a known issue with the pre-release Windows SDK for Windows Server 2008 and .NET Framework 3.5 that may prevent your sample or code from running. This will be fixed in a future release. In some cases, for VCBuild to run properly, vcprojectengine.dll needs to be registered manually. Without registering vcprojectengine.dll, VCBuild.exe could fail with errors such as:
On compile:
warning MSB3422: Failed to retrieve VC project information through the VC project engine object model. System error code: 127.
On upgrade:
Failed to upgrade project file 'ping.vcproj'. Please make sure the file exists and is not write-protected.
To workaround this issue, vcprojectengine.dll must be manually registered. From a Windows SDK command line window (in Vista, right-click SDK CMD Shell shortcut and choose run as administrator), run:
On an X86 or IA64 machine:
cd %mssdk%\VC\bin
regsvr32 vcprojectengine.dll
On an X64 machine:
cd %mssdk%\VC\bin\X64
regsvr32 vcprojectengine.dll
A window should pop up to verify that vcprojectengine.dll has been registered.
Comments
Anonymous
August 17, 2007
PingBack from http://msdnrss.thecoderblogs.com/2007/08/18/workaround-vcbuild-fails-to-compile-or-upgrade-projects-in-sdk/Anonymous
August 17, 2007
There is a known issue with the pre-release Windows SDK for Windows Server 2008 and .NET Framework 3