When I run the Sandcastle Help File Builder project file (for example, myproject.shfbproj
) using Windows CMD, I get an annoying issue: $(SolutionDir)
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
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" />