#1
|
|||
|
|||
Actions finding MSBuild.exe
How is MSBuild located by the Make VS.NET/2005 actions?
On a new setup my VS2005 projects are failing to build. If I override the default handling by pointing to the actual location (C:\Windows\Microsoft.NET\Framework\v2.0.50727\MSB uild.exe) then it works, but removing that and relying on the detection fails. Any suggestions? Thanks. Last edited by DuncanL; 04-09-2008 at 05:24 AM. |
#2
|
|||
|
|||
It looks for the registry value HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramewor k\InstallRoot, then iterates over all subdirectories of the folder in that registry value for the newest framework version (excluding v3.0 since it doesn't include msbuild.exe), and using the dir+msbuild.exe if found.
Please ZIP and send to support@kinook.com or post: 1) The info from Help | About | Install Info 2) The .bld file 3) A build log file 4) The .sln file and project files (no source code files) 5) Export of registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramewor k 6) Recursive directory listing of .NET Framework path (i.e., dir /s C:\WINDOWS\Microsoft.NET\Framework\ > out.txt from a Command Prompt) Thanks. |
#3
|
|||
|
|||
Very odd... unless I'm going blind it all looks OK. I will e-mail you the requested information.
|
#4
|
|||
|
|||
The problem is that on your system, there is a v3.5 subfolder with no msbuild.exe in it (which is normally the case if .NET 3.5 has been installed). Either delete/move that folder or install VBP v6.7 -- one of the changes in 6.7 is to use msbuild.exe from .NET v2.0 for building VS2005 solutions even if .NET v3.5 is detected.
|
#5
|
|||
|
|||
Thank you very much. For now we have just removed the folder. If we need .NET 3.5 in the future then we will have to update VBP.
|
|
|