msbuild error: The property DirectoryName does not exist or was not found

3
votes

This is my first attempt to configure an automated build on Visual Studio Online.

After creating a new build, I queued it to run. The first step was successfully completed (Get sources). Now I am experiencing and error in the build step. Here is a small snippet including the message:

782 2015-08-31T16:30:52.4324803Z Executing the powershell script: C:\LR\MMS\Services\Mms\TaskAgentProvisioner\Tools\tasks\VSBuild\1.0.13\VSBuild.ps1

783 2015-08-31T16:30:54.0509690Z ##[error]The property DirectoryName does not exist or was not found.

784 2015-08-31T16:30:54.1321607Z C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe "C:\a\5bc0b6a3\MySolution" /nologo /m /nr:false /fl /flp:"logfile=C:\a\5bc0b6a3\MySolution.log" /dl:CentralLogger,"C:\LR\MMS\Services\Mms\TaskAgentProvisioner\Tools\agent\worker\Microsoft.TeamFoundation.DistributedTask.MSBuild.Logger.dll"*ForwardingLogger,"C:\LR\MMS\Services\Mms\TaskAgentProvisioner\Tools\agent\worker\Microsoft.TeamFoundation.DistributedTask.MSBuild.Logger.dll" /p:platform="any cpu" /p:configuration="debug" /p:VisualStudioVersion="14.0"

785 2015-08-31T16:30:54.2859104Z MSBUILD : error MSB1009: Project file does not exist.

I have searched for the DirectoryName string in the entire solution with no success and have now idea what it means.

Compilation works fine on my PC and I have no clue where to start looking at.

Any ideas?

2
visual-studiotfsmsbuildcontinuous-integrationvisual-studio-2015

2 Answers

4
votes

You're missing the real error: 

785 2015-08-31T16:30:54.2859104Z MSBUILD : error MSB1009: Project file does not exist.

You need to specify the path to a solution file. You can see that you're not:

C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe "C:\a\5bc0b6a3\MySolution" /nologo /m /nr:false /fl /flp:"logfile=C:\a\5bc0b6a3\MySolution.log" /dl:CentralLogger,"C:\LR\MMS\Services\Mms\TaskAgentProvisioner\Tools\agent\worker\Microsoft.TeamFoundation.DistributedTask.MSBuild.Logger.dll"*ForwardingLogger,"C:\LR\MMS\Services\Mms\TaskAgentProvisioner\Tools\agent\worker\Microsoft.TeamFoundation.DistributedTask.MSBuild.Logger.dll" /p:platform="any cpu" /p:configuration="debug" /p:VisualStudioVersion="14.0"

You can just specify **\*.sln for the "Solutions" parameter and it will discover and build all of the solutions in the workspace you mapped. If you need to get more specific, you can do that as well.

0
votes

The folder in which the solution file is should be in or below one of the paths as defined in the mappings under the 'Repository' tab, otherwise the 'Project file does not exist' error will show up also.