Closed nhirschey closed 10 months ago
Yes, this is expected. The way a Directory.Build.props
file works is that it adds everything it contains to all the child *proj
files in that directory. Only actual projects are being cracked, and so these properties won't flow through as globals if there is nothing to crack.
We could probably try and find a Directory.Build.props
and process it as XML if there were no projects.
There should be a fix for this in https://www.nuget.org/packages/fsdocs-tool/20.0.0-alpha-007.
Works great. Thank you! With this and other improvements I can now use the default theme on my teaching site.
It is useful to build a blog-style site using this tool, with configuration handled by
Directory.Build.props
. This is not possible with the default theme becauseDirectory.Build.props
is ignored when there is no project or solution. The generated site thus has broken links forFsDocsLicenseLink
,FsDocsReleaseNotes
, andRespositoryLink
. The command line tool also says the values aren't set even when they are:For instance with this in directory build props, I get the below error: