The build script uses MSBuild to build the FSharpComposableQuery.fsproj project file. Although the process builds the library, it does not generate the XML documentation file FSharpComposableQuery.XML as required by the docs generation script.
Inspecting the project file properties reveals it should create such an Xml documentation file when built, and indeed doing this from Visual Studio actually creates the file.
It is interesting why the build script does not instruct the compiler to generate docs. It is its job to parse the project file and pass all relevant options to MSBuild.
One can confirm there is a discrepancy in the parameters passed to MSBuild by examining them in both cases: the IDE passes the additional switch --doc:..\..\bin\FSharpComposableQuery.XML as compared to FAKE v3.2.3 (and v2.1.7, too).
The build script uses MSBuild to build the
FSharpComposableQuery.fsproj
project file. Although the process builds the library, it does not generate the XML documentation fileFSharpComposableQuery.XML
as required by the docs generation script.Inspecting the project file properties reveals it should create such an Xml documentation file when built, and indeed doing this from Visual Studio actually creates the file.
It is interesting why the build script does not instruct the compiler to generate docs. It is its job to parse the project file and pass all relevant options to MSBuild.
One can confirm there is a discrepancy in the parameters passed to MSBuild by examining them in both cases: the IDE passes the additional switch
--doc:..\..\bin\FSharpComposableQuery.XML
as compared to FAKE v3.2.3 (and v2.1.7, too).