20080710 vs2008 lc.exe 错误 67 任务失败，原因是未找到“LC.exe”，或未安装正确的 Microsoft Windows SDK。该任务正在注册表项 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v6.0A 的 InstallationFolder 值中指定的位置下的“bin”子目录中查找“LC.exe”。您可以通过执行下列操作之一来解决这一问题: 1) 安装 Microsoft Windows SDK for Windows Server 2008 和 .NET Framework 3.5。 2) 安装 Visual Studio 2008。 3) 将上面的注册表项手动设置到正确的位置。 4) 将正确位置传入任务的“ToolPath”参数。 Platform.Winform Error 1 Task failed because "LC.exe" was not found, or the correct Microsoft Windows SDK is not installed. The task is looking for "LC.exe" in the "bin" subdirectory beneath the location specified in the InstallationFolder value of the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v6.0A. You may be able to solve the problem by doing one of the following: 1) Install the Microsoft Windows SDK for Windows Server 2008 and .NET Framework 3.5. 2) Install Visual Studio 2008. 3) Manually set the above registry key to the correct location. 4) Pass the correct location into the "ToolPath" parameter of the task. Cypher1 把水晶报表勾选重装 OK 酷睿T5750比P3.0G真是快多了····· I reinstalled the .NET 3.5 framework, but made no difference. ``````````````````````````````` Nevermind. I reinstalled the SDK again and it works now. Problem #3: Cannot find the .NET 2.0 SDK The first .csproj that get's build gives the following warning early in the build: Could not locate the .NET Framework SDK. The task is looking for the path to the .NET Framework SDK at the location specified in the SDKInstallRootv2.0 value of the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework. You may be able to solve the problem by doing one of the following: 1.) Install the .NET Framework SDK. 2.) Manually set the above registry key to the correct location. I dutifully checked the registry and found that the required key was missing. Further research reveals that while VS2008 does support builds targeting the 3.0 framework (as does my build), it always builds again the v3.5 framework which ships with the compiler. The compiler just figures out what stuff to leave out so that assemblies targeted for v2.0 or v3.0 still build and run. The problem with my .csproj files is that they are not upgraded to VS2008 (and shouldn't be) and so they are still looking for the old v2.0 SDK folder. That should be an easy fix... I downloaded the .NET 2.0 SDK from Microsoft and installed it. I verified the expected registry key is created and pointing to the installation folder. Good. Build again. Voila! No more ugly warning. But quickly another failure. This bug is being resolved as “External”. This means that your issue is being moved from the Visual Studio bug database into the Windows SDK bug database. We will close your original bug. Because the bug databases don’t talk to each other at present, further communications about this issue will need to be in email in order for me to see them. You can post your response here on the Connect, but you must also email me (karinm at microsoft dot com) to ensure I get your communication. I’ll post a response on the Connect Site and email you back directly. In answer to your issue: The Windows SDK Configuration Tool works by changing the CurrentInstallFolder value in the registry. VS looks for the "currentInstallFolder" value first in The standalone Windows SDK, and the Windows SDK content embedded in Visual Studio sets both keys, but in your situation it appears that the SDK Configuration Tool might only be updating HKEY_LOCAL_MACHINE. Therefore, whichever SDK was installed last will be the one set in the CurrentInstallFolder. Using the SDK Configuration Tool will have no effect. The workaround is to update HKEY_CURRENT_USER to point to the version of the SDK that you wish to build with: 1. HKEY_CURRENT_USER\Software\Microsoft\Microsoft SDKs\Windows\ CurrentInstallFolder = C:\Program Files\Microsoft SDKs\Windows \v6.0A\ to build with the Windows SDK content included in VS2008; or Please give this a try and let me know if it fixes your issue. Please contact me directly at karinm at microsoft dot com.
The .NET Framework 3.5 is still based on CLR 2.0 + updates that 3.5 ships with it. .NET Framework 3.5 ships with Express, but you can get it stand alone with the compilers (without IDE integration until Visual Studio 2008) by downloading it from: http://www.microsoft.com/downloads/details.aspx?FamilyId=333325FD-AE52-4E35-B531-508D977D32A6&displaylang=en So the only thing which seemed to work is re-installing the SDK again. It can be found here. 1. Correct link http://blogs.msdn.com/windowssdk/archive/2008/02/07/windows-sdk-rtms.aspx 一、如果使用MSBuild任务的话，需要把ThoughtWorks.CruiseControl.MSBuild.dll文件拷贝到工作目录下才能正常编译。 ***EndOfSession***[07/08/08,19:20:41] MSITOSIT: [2] ERROR processed; exception was thrown for retail build 字体：大 中 小 |
 | 永久地址 http://www.shengfang.org/blog/p/20080710vs2008lcexe.php |
 | 引用地址 http://www.shengfang.org/blog/tb.php?tb_id=1235216942 |
2009年2月21日19:49星期六 [Info资料] 
