However, Sandcastle Help File Builder. View default.aspx.cs which contains the C# for the site. 3 thoughts on “SandCastle – Creating a website”. Sandcastle Help File Builder – the GUI. The Sandcastle Styles package is a collection of patches to the core Sandcastle’s presentation component. If you don’t install it you may get either poor or even faulty rendering of your output, possibly without realizing it. The SHFB Installation Instructions certainly mention this, but you might miss that. A Guide to Sandcastle - Part 1 - Introduction. I should remind the reader that using the Sandcastle Help File Builder is not required to. By default, on the. Browse files. Add Sandcastle documentation artefacts. Large diffs are not rendered by default. + // files created by the help file builder.

I've created an NDoc-like GUI front-end plus a command-line builder tool for automating help file builds with Sandcastle. It's available at: Using the help file builder provides the following advantages: • The GUI interface is almost identical to the NDoc interface so anyone familiar with NDoc should be quite comfortable using it. • You can import several settings from an existing NDoc project to start a new Sandcastle Help File Builder project. • The builder will automatically locate both Sandcastle and the HTML help compiler by looking in the system path and in the Program Files special folder on all fixed hard drives. Properties are also supplied for you to specify the paths in the off-chance that it cannot locate them automatically. Downloads. • There is built-in support for documenting multiple assemblies and producing a single-help file for them.

The assemblies to document can be executable (.EXE) or library (.DLL) assemblies. • The settings are saved in a project file and the help file can be built from within the GUI or you can add a post-build step to a Visual Studio project that runs the command line tool to build it for you using the same project file. • The intermediate files used to create the help file are placed in a working folder beneath an output folder of your choosing. They can be automatically removed after a successful build or kept around for further modifications.

• The build process provides full logging and error handling. All output from the build is stored in a text file in the output folder. • Several of the NDoc features that I use most often have been built into the Sandcastle help file builder including: • The ability to turn off documentation of attributes.

• Automatic determination of the default topic for the help file. • Inclusion of additional help file content (i.e.

Your own HTML pages, images, etc). Unlike NDoc, you can also take steps to have the extra HTML pages included in the help file's table of content. • You have control over the copyright text and e-mail address that appear in the footer of each page. • You also have control over the help file name and title. • I have added features to let you control the language of the help file. Since I only speak English, those are the only resource files available at the moment.