Making a local test build before pushing changes
Before you push your changes to the repository, it is often a good idea to make a test build on your local machine. This is especially the case if your changes involve adding or removing files, adding cross-references, changing headers, and/or updating a toc.yml file.
To be able to make a local test build, you need to have DocFX installed. DocFX is the static website generator that is used under the hood to create the https://docs.dataminer.services/ website.
Installing and configuring DocFX
Install .NET 6.0 SDK or higher from dotnet.microsoft.com.
Open a command prompt and enter the command
dotnet tool update -g docfx
Test whether DocFX was installed correctly by entering
docfx --version
.If information similar to the following text is returned, DocFX was installed correctly:
2.75.1+6aa697f56975e85e82c5a6b81b71157c77302270 ...
Tip
Alternative ways to install DocFX can be found on the DocFX website.
Note
If you use this "dotnet" command, it is no longer necessary to add the DocFX folder to the Windows Path variable as was the case in the past. If you configured this earlier, we recommend that you remove this folder from the Path variable again and reboot.
Making a test build
Making a test build using buildDocs.cmd
Make sure .NET 6.0 SDK or higher is installed on your machine. You can download the latest version from dotnet.microsoft.com.
Go to the root folder of the repository on your local machine, e.g.
C:\GitHub\dataminer-docs\dataminer-docs
.Double-click the file buildDocs.cmd.
This will open a command window where the following commands will run:
dotnet restore "src/NuGetPackages"
dotnet build "src/NuGetPackages" --configuration Release
docfx metadata
docfx build
docfx serve _site
In a browser, go to http://localhost:8080/ to preview the website.
Note
Using the search box when viewing the test website on http://localhost:8080/ will not return any pages from the test website. The search engine only indexes the published content on https://docs.dataminer.services/ and will, as such, only return pages from that website.
When you have finished previewing the website, close the command window.
Note
If port 8080 is not available, you will need to run buildDocs.cmd from a command prompt with the correct port as an argument, e.g. buildDocs 8081
.
Important
If you make test builds often, you may need to occasionally clear the files in the \dataminer-docs\obj\.cache\build\
folder of your local version of the documentation. Depending on your DocFX version, these can pile up and take up a large amount of memory in the long run.
Making a test build in the Visual Studio Code terminal
If you make repeated test builds to check changes you have made, and you are only making changes to markdown files, you can also run these commands manually in the Visual Studio Code terminal. This has the advantage that you do not need to run all of the commands every time, so your test builds can be generated more quickly.
If no Terminal pane is open in Visual Studio Code, go to Terminal > New Terminal.
In the Terminal pane, do the following:
Enter
clear
to clear the terminal.Enter the following commands:
dotnet restore "src/NuGetPackages"
dotnet build "src/NuGetPackages" --configuration Release
docfx metadata
docfx build
docfx serve _site
Note
- The first three commands are needed to generate the API docs. If you make repeated test builds to check changes you have made, and you are only making changes to markdown files, you can skip these three commands after your first build.
- This step requires that .NET 6.0 SDK or higher is installed on your machine. If this is not installed yet, you will get a build error. You can download the latest version from dotnet.microsoft.com.
In a browser, go to http://localhost:8080/ to preview the website.
Tip
If you are not able to access localhost:8080, you can specify a different port by entering e.g.
docfx serve _site -p 8090
.When you have finished previewing the website, in the Terminal pane, press Ctrl+C to exit the preview mode.
Note
Using the search box when viewing the test website on http://localhost:8080/ will not return any pages from the test website. The search engine only indexes the published content on https://docs.dataminer.services/ and will, as such, only return pages from that website.
Important
If you make test builds often, you may need to occasionally clear the files in the \dataminer-docs\obj\.cache\build\
folder of your local version of the documentation. Depending on your DocFX version, these can pile up and take up a large amount of memory in the long run.