You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I get an error when I try to build a project. The error says that the file "...\TemplatesPlaceHolderNode.aml" could not be found.
In File SHFB/SHFB/Source/SandcastleBuilderUtils/ConceptualContent/TokenCollection.cs
please change Line 443 from: templateText = Utility.ReadWithEncoding(builder.TemplateFolder + "PlaceHolderNode.aml",
to: templateText = Utility.ReadWithEncoding(Path.Combine(builder.TemplateFolder, "PlaceHolderNode.aml"),
As a quick fix i copied the .aml file to the parent directory and renamed it to "TemplatesPlaceHolderNode.aml". Now I get another error that there is an unknown substitution tag "SHFBFolder" (BE0020). But I think it´s a different issue.
The text was updated successfully, but these errors were encountered:
The placeholder is used when you have a topic in the content layout file without an associated file. You can work around it by assigning a blank topic file to it.
The substitution tag error is probably caused by an outdated code block component configuration in the project. Just open the code block component configuration and save it again to have it correct the settings. See the release notes related to breaking changes.
I get an error when I try to build a project. The error says that the file "...\TemplatesPlaceHolderNode.aml" could not be found.
In File SHFB/SHFB/Source/SandcastleBuilderUtils/ConceptualContent/TokenCollection.cs
please change Line 443 from:
templateText = Utility.ReadWithEncoding(builder.TemplateFolder + "PlaceHolderNode.aml",
to:
templateText = Utility.ReadWithEncoding(Path.Combine(builder.TemplateFolder, "PlaceHolderNode.aml"),
As a quick fix i copied the .aml file to the parent directory and renamed it to "TemplatesPlaceHolderNode.aml". Now I get another error that there is an unknown substitution tag "SHFBFolder" (BE0020). But I think it´s a different issue.
The text was updated successfully, but these errors were encountered: