This article explains how to clone DevExpress End-User documentation sources and how to create your own documentation websites and help files for projects based on DevExpress technologies. It also provides links to a sample pre-built website and PDF files.
For Developer Documentation with API Reference see https://docs.devexpress.com.
DevExpress products for WinForms, WPF and ASP.NET WebForms/MVC.
By accessing this repository, you agree to the terms of the DevExpress End-User Documentation License Agreement.
Do one of the following to view the End-User Documentation content:
- Browse this repository's content directly. Start with index.md.
- View the sample pre-built website at devexpress.github.io/dotnet-eud.
- Download these PDF files:
Documents in this repository are written in markdown. You can manually copy the information to your own help file.
The repository also includes a docfx.json file. You can use DocFX and wkhtmltopdf to convert this file from a set of topics to an HTML website or a PDF file.
Follow the steps below to create a documentation website for your application.
-
Download and install the latest version of DocFX.
-
Copy the repository to your computer and checkout the branch corresponding to the version of DevExpress controls your application uses. Do not use the master branch because it represents the version currently under development.
git clone https://github.com/DevExpress/dotnet-eud.git --branch 18.1If you do not have Git installed, use the GitHub web interface to select the branch and then download and extract the ZIP archive.
-
You can make the following changes to the documentation, or skip this step if you want to reuse the end-user documentation as is:
- remove unnecessary files;
- add new documents to your application;
- change screenshots to match your app's UI;
- create a custom DocFX template.
You should update the toc.yml (table-of-content) files if you added or removed topics.
-
Open a console window, change the current directory to the repository root folder and call the DocFX executable with the build and docfx.json parameters. DocFX will place the generated documentation content into the _site folder. Add the
--serveswitch to preview the generated website at http://localhost:8080 once the build process is complete.docfx.exe build docfx.json --serve -
Finally, deploy the created documentation to a web server or browse the documentation directly from local file system. Since DocFX creates static HTML files only, no additional deployment or configuration steps are required.
If your end users require a printed version, you can create a PDF file:
- Ensure that you can successfully build a website with DocFX (see the previous section).
- Download and install wkhtmltopdf.
- Open a console window and add the wkhtmltopdf executable path to the %PATH% environment variable:
set PATH=%PATH%;C:\Program Files\wkhtmltopdf\bin - Change the current directory to the repository root folder and call the DocFX executable with the pdf and docfx.json parameters. This generates a _pdf subfоlder with a PDF file for each included table-of-contents file.
docfx.exe pdf docfx.json
Below are the common issues you can face when building this repository's documentation.
-
Reduce your working directory's full path (move the repository closer to a drive root).
See also: dotnet/docfx#156
-
Ensure that wkhtmltopdf is installed and its executable path is correctly added to the %PATH% environment variable.
See also: Generate PDF Documentation
-
The table of contents is not displayed when browsing the generated documentation from the file system
Your browser security configuration may restrict executing the JavaScript code that accesses your local files (the table of contents is in a separate toc.html file when using the default DocFX template). In this case, you can use the statictoc template instead. To switch to this template, add
--template statictocto the docfx.exe parameters:docfx.exe build docfx.json --template statictocThe table of contents is embedded into each topic with this template which increases the build time and HTML file sizes. Alternatively, you can override the browser's restrictions (which may be unsecure). For example, Google Chrome and Microsoft Edge accept the
--allow-file-access-from-filescommand line switch which allows loading local files.We recommend using the
--serveDocFX switch to preview documentation, and then share it with end users via a web server instead of browsing the file system.
If your issue is not listed, you can submit a new issue to this repository or contact us via the DevExpress Support Center. You can search the DocFX issues list, or try building the docfx-seed sample documentation project to check if your issue is specific to this repository.
If you require End-User documentation for v17.1 or earlier, download End-User Documentation Installer containing CHM and PDF files. Markdown is not available for these versions.
| Version | Installer |
|---|---|
| v17.1 | DevExpressEndUserDocs171.exe |
| v16.2 | DevExpressEndUserDocs162.exe |
| v16.1 | DevExpressEndUserDocs161.exe |
| v15.2 | DevExpressEndUserDocs152.exe |
| v15.1 | DevExpressEndUserDocs151.exe |
| v14.2 | DevExpressEndUserDocs142.exe |
| v14.1 | DevExpressEndUserDocs141.exe |
| v13.2 | DevExpressEndUserDocs132.exe |
| v13.1 | DevExpressEndUserDocs131.exe |
| v12.2 | DevExpressEndUserDocs122.exe |
| v12.1 | DevExpressEndUserDocs121.exe |
You are free to download these files and distribute them to your end users. However, Developer Express Inc. has the right to change or remove these files without notice.