ptn715

Hi All,

After I created a new Team Build Type and executed Build Team Project and I got the Report

Summary : Failed

Build Steps:

Initializong build: Failed

Failed.

Please help me how to find the reason why it failed and how to fix the problems.

Thanks,

Ptn715



Re: Team Foundation Server - Build Automation Failed When I execute Build Team Project

Patrick Carnahan - MSFT

Is there anything at the drop location Typically there will be a build log generated for you, unless there was a problem accessing the drop location. If there is nothing at the drop location of the build then you should take a look at the build directory on the build machine. The specific file you should look for is <Build Location Root in Build Type>\<TeamProject Name>\<Build Type Name>\BuildType\BuildLog.txt. If this file does not exist either, then you will want to be sure of the following:

Does the drop location you specified exist Did you provide appropriate permissions on the drop location You should be aware that the sharing permissions and NTFS permissions are in fact different; you will need to apply a full access ACE to the service account in both the 'Sharing' tab and the 'Security' tab, otherwise it will not work.

See if the build log exists at the drop; if not, look at the build location; if nothing there, ensure that you have appropriate permissions. If none of this helps diagnose your issue, please let me know so I can provide further guidance.

Thanks,

Patrick





Re: Team Foundation Server - Build Automation Failed When I execute Build Team Project

ptn715

Hi Patrick,

Thanks for helping. It fixed now but when execute Build Team Project it faild and I got the error

Solution: , Project: Web.sln, Compilation errors and warnings

C:\BuildServer\Builds\Hosted\Security WS\Sources\Hosted\Shared\WebServices\Security\Web\Web.csproj(125,11):

error MSB4019: The imported project "C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\WebApplications\Microsoft.WebApplication.targets" was not found.

Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.

I am a new with Team Build, please help me how to fix this problem

Thanks in advanced

Ptn715





Re: Team Foundation Server - Build Automation Failed When I execute Build Team Project

Patrick Carnahan - MSFT

You will need to install the web application add-in for Visual Studio 8.0 on the build machine in order for this to work. I would guess that it builds on your local machine just fine, and that the build machine is a remote machine

Team Build makes very heavy use of MSBuild, which is very similar to ant/nant in syntax. I would recommend taking some time to read up on the MSBuild framework as any advanced customization of the build process will require knowledge of it. The general idea is that MSBuild has targets files, which are files that define how to go about processing a file and how the build process should be performed. Each individual project file will generally import a targets file and has the ability to add additional behavior through target/property overrides. In your particular scenario, the targets file in question is not one of the standard targets files installed with MSBuild and therefore needs to be installed separately from the link provided.

Patrick





Re: Team Foundation Server - Build Automation Failed When I execute Build Team Project

ptn715

Hi Patrick,

I installed the web application add -in for Visual Studio 8.0 on the build machine. The build machine is a remote machine. I re-executed Build Team Project and got the error in Release.txt. Can you tell me how to get these dll references in the build machine I mean I have to copy these dll files from my laptop to the build machine

Thanks,

Ptn715

Solution: Web.sln, Project: Web.csproj, Compilation errors and warnings

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets(0,0): warning MSB3245:

Could not resolve this reference. Could not locate the assembly "Microsoft.Practices.EnterpriseLibrary.Common, Version=2.0.0.0, Culture=neutral, PublicKeyToken=dcfc8abdd1cc2742, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets(0,0): warning MSB3245:

Could not resolve this reference. Could not locate the assembly "Microsoft.Practices.EnterpriseLibrary.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=dcfc8abdd1cc2742, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets(0,0): warning MSB3245:

Could not resolve this reference. Could not locate the assembly "Teleflora.Hosted.Shared.Logging, Version=1.0.1.9, Culture=neutral, PublicKeyToken=91a3896bf8388a62, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.





Re: Team Foundation Server - Build Automation Failed When I execute Build Team Project

DQM

Your dll references should be setup differently in your web project. Here's what we are doing.

Beneath the project folder we have another folder called ThirdParty. We dump all dlls like the EntLib ones in that folder and add it to source control. The project references dlls in this folder. Make sure references are relative and not absolute path.

When you do a build this folder should get copied down to the build machine.

another approach that has been suggested is to use a common shared folder on a server as the reference path. Using that, the dll path references are constant no matter which machine is used to compile - your laptop or the build machine.





Re: Team Foundation Server - Build Automation Failed When I execute Build Team Project

ptn715

Thanks DQM, it worked now. I'm very appreciate with your and Patrick Carnahan's help

Ptn715