Set PublishReferencesDocumentationFiles=false in fake-cli#2829
Set PublishReferencesDocumentationFiles=false in fake-cli#2829xperiandri merged 1 commit intofsprojects:masterfrom
Conversation
|
Maybe they help for API-docs (https://fake.build/reference/index.html) or user tool-tips? |
|
The documentation XML files in the individual library nuget packages can be used for intellisense and such, and the doc comments themselves are used by the published documentation, but I didn't think the files in the dotnet global tool would be loaded as the package isn't attached to consuming projects like a library is (naybe I'm wrong there though) |
|
Many people still use Fake not via cli-tool but as "dotnet fsi build.fsx" with independent library dependencies, and I think xml-docs there will help. |
|
@Numpsy Do you disable XML docs output only for CLI tool? |
That was the intent - e.g. in my local build the Fake.DotNet.Cli NuGet package contains the documentation XML file, but the fake-cli package doesn't -
|
Numpsy
force-pushed
the
doc_comments
branch
from
66b5ec5 to
88b8c86
Compare
|
@Numpsy let's merge? |
Test Results 9 files 9 suites 36m 23s ⏱️ Results for commit 9349413. ♻️ This comment has been updated with latest results. |
xperiandri
force-pushed
the
doc_comments
branch
from
429cf51 to
9349413
Compare
3 participants
Description
Just a thought when looking at the build output for fake-cli - Is there a need to have the XML documentation files for a bunch of the FAKE libraries included in the fake-cli NuGet package?
e.g.
