$(SolutionDir) MSBuild property incorrect when running Sandcastle Help File Builder via CMD

Question

When I run the Sandcastle Help File Builder project file (for example, myproject.shfbproj) using Windows CMD, I get an annoying issue: $(SolutionDir) has the same value as $(ProjectDir), and this means that project documentation sources won't build correctly, because I'm adding custom targets which already use $(SolutionDir).

If I build the whole Sandcastle Help File Builder from Visual Studio it builds successfully.

I'm using the following command (executed from the directory where the project is stored):

"C:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe" /p:Configuration=Development myproject.shfbproj

Is there a workaround for this?

Solution 1

While @m0sa has pointed out a very obvious fact (since I'm building the Sandcastle Help File Builder project, there's no actual solution directory), the issue was also happening during a TFS Build when building the solution where the so-called documentation project resides.

For now I've managed to solve the issue using a nasty workaround: adding a SolutionDir property in each C# project that needs to be built as part of documentation project:

  <PropertyGroup>
    <SolutionDir>$([System.IO.Path]::GetDirectoryName($(MSBuildProjectDirectory)))\</SolutionDir>
  </PropertyGroup>

Since my solution file will always be located in the parent directory of Sandcastle Help File Builder project directory, in my case this workaround works...

Now referenced projects as documentation sources are able to import a custom project where I define common MSBuild properties, both in Visual Studio builds or external ones:

<Import Project="$(SolutionDir)MSBuild\Common.properties" />

Solution 2

You only get the the correct $(SolutionDir) if you're building your solution (.sln file). The .shfbproj is a project file, and as such has no reference to its parent solution. You can try specifying the $(SolutionDir) in your command line explicitly:

msbuild /p:Configuration=Development /p:SolutionDir=MySolutionDir myproject.shfbproj

For reference: $(SolutionDir) and MSBuild

Comments

[Matías Fidemraizer]

I tried this with no luck. I managed to workaround the issue defining the whole solution dir in each csproj before I need the right $(SolutionDir) value..

[Alex]

Needed quotes to work for me - /p:SolutionDir="MySolutionDir" rather than /p:SolutionDir=MySolutionDir

[sorosh_sabz]

I think it is very better to define some of these variable as predefined variable by Microsoft by default.

[SandRock]

This also works when running msbuild /target:Package xxx.csproj