MSB3073: 'PreBuildEvent' failed with error '1'

Question

I'm in the Build Business and one of my teams is still using TFS2005. They've now agreed to upgrade, but they want to go straight to 2010. :-(

I've built them a 64 bit build server and have been trying to get builds working using TFS2008 SP1 for now. Most projects build but one has me tearing my hair out with the above error.

If I run the command from the CMD window on the build server, it reports;-

'"C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\al.exe"' is not recognized...

It's quite right, of course - the assembly linker is under the Microsoft SDKs folder. I've tried setting ALToolPath environment variable, using different versions of .NET, but to no avail.

Ideas anyone?

Answer 1

If you are using MSBuild, I would suggest you to try MSBuild category for better support.

http://social.msdn.microsoft.com/forums/en-US/msbuild/threads/

And please send more information about this issue, such as logs. I see you call a al.exe, what's it?

There is a Team Foundation Server forum for your reference too.

http://social.msdn.microsoft.com/Forums/en-US/tfsgeneral/threads

Hope it helps.

---

Best Regards,
Rocky Yue[MSFT]
MSDN Community Support | Feedback to us

Answer 2

I've created this forum in the .Net forum (isn't MSBuild part of .net??) and been advised to create it here.

I'm in the Build Business and one of my teams is still using TFS2005. They've now agreed to upgrade, but they want to go straight to 2010. :-(

I've built them a 64 bit build server and have been trying to get builds working using TFS2008 SP1 for now. Most projects build but one has me tearing my hair out with the above error.

If I run the command from the CMD window on the build server, it reports it can't find the Assembly Linker;-

'"C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\al.exe"' is not recognized...

It's quite right, of course - the assembly linker is under the Microsoft SDKs folder. I've tried setting ALToolPath environment variable, using different versions of .NET, but to no avail.

Ideas anyone?

Answer 3

Hi Build,

Al.exe is a .Net Framework SDK tool and is not included in .Net Framework 2.0. You will need to install the .Net Framework SDK to get AL.exe.

You can download the SDK from http://www.microsoft.com/downloads/details.aspx?FamilyID=fe6f2099-b7b4-4f47-a244-c96d69c35dec&DisplayLang=en

---

Lucy Liu [MSFT]
MSDN Community Support | Feedback to us

Answer 4

Hi, Lucy-liu,

Thank you for your reply. Sorry for the delay but other fires needed fighting!

I had already installed that SDK, and the patch. I had also already installed TFS 2010 and TFS 2008 SP1.

I appreciate your help. Any more ideas?

Answer 5

Hi,

I have reinstalled all of the 2008 .Net SDK but the problem still persists. This is jeopardising our upgrade to 2010.

Please could someone help with this? How do I tell MSBuild that the Assembly linker is in the SDK and not in the .Net folders?

Answer 6

Hi, Folks,

I can close this, now.

For no particular reason that I can think of, I looked at this project again using TFS 2005. Selected "Properties" from the drop down, and get a different set of properties than you get with TFS 2008, which has a dialog. The TFS 2005 PreBuildEvent my colleague added a command which explicity calls AL.exe on the above path. I corrected the path and all is well. Problem fixed.

So, Messrs Microsoft, why do we have to have two sets of properties on a .wdproj??? Why change the function of the dropdown??? Why move AL.EXE???