-
Notifications
You must be signed in to change notification settings - Fork 506
Conversation
Caboodle/Caboodle.csproj
Outdated
This runs during the package phase. | ||
============================================================ | ||
--> | ||
<Target Name="AddMDocFilesToPackage" BeforeTargets="_GetBuildOutputFilesWithTfm" DependsOnTargets="SetupMDoc"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this not depend on GenerateDocsWithMDoc
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No as they are separate steps.
GenerateDocsWithMDoc
runs as part of the core compilation of the individual assemblies. AddMDocFilesToPackage
is a special task that is run when the .nuspec is being created. If there is a dependency, then it will fail as the Pack
task does not actually start the compile.
An interesting thing happens on mac... After running the Not sure why, but since the job has already run, it should be safe to ignore.
https://gist.github.com/mattleibow/0942417c7b8aebadfb9e7184eba9a562 |
build |
Closes #16 |
Merge xamarin:main into dimonovdd:main
Building the project will automatically run mdoc to generate the docs.
Once the project is compiled, a task can be run to take all the output assemblies and update the docs:
This is for the #16 issue.
An example case of using everything could be this:
msbuild /p:Configuration=Release
)msbuild /t:MDocUpdateDocs /p:Cnfiguration=Release
)NOTE: The
UpdateDocsWithMDoc
task is best run on Windows as the UWP library has to be processed. However, if this is run on macOS, then an assembly element will be missing from the./docs/en/index.xml
file. Be careful not to commit this.