Add licensing notice to HeatWave Build Tools

FireGiantDocs · FireGiantDocs · commit d81e19c2f0af · 2025-11-08T00:50:17.000-08:00
diff --git a/src/content/docs/heatwave/build-tools/driver.md b/src/content/docs/heatwave/build-tools/driver.md
@@ -8,6 +8,10 @@ sidebar:
 The FireGiant Driver Extension can install, repair, upgrade, uninstall, and roll back kernel and file system drivers.
 This WiX Extension is very lightweight and robust and avoids all the complexity DifxApp requires to install plug and play (PnP) drivers. All you need is your system driver, FG-WiX and one line of XML.
 
+:::caution[Licensed feature]
+Like the other features in HeatWave Build Tools, a license file is required to use FireGiant Driver Extension. See the [FireGiant licensing documentation for more information](../firegiant-licensing/).
+:::
+
 Here is a snippet of .wxs code that can install a simple kernel driver:
 
 ```xml title=FooDriver.wxs
diff --git a/src/content/docs/heatwave/build-tools/firegiant-licensing.md b/src/content/docs/heatwave/build-tools/firegiant-licensing.md
@@ -4,7 +4,7 @@ sidebar:
   order: 1
 ---
 
-The HeatWave Build Tools require a license file, a .fglic file, to be available on developer and build machines. The license file is only used by the build tools and does **not** need to be distributed with the built installation packages. You can download your license file from [your FireGiant Account's License page][lp].
+The HeatWave Build Tools require a license file, a `.fglic`, to be available on developer and build machines. The license file is only used by the build tools and does **not** need to be distributed with the built installation packages. You can download your license file from [your FireGiant Account's License page][lp].
 
 
 ## License file placement
diff --git a/src/content/docs/heatwave/build-tools/harvesting/index.md b/src/content/docs/heatwave/build-tools/harvesting/index.md
@@ -6,6 +6,10 @@ sidebar:
 
 Advanced Harvesting gathers resources from MSBuild project references, folders and self-registration to generate .wxs code that installs those resources. Advanced Harvesting takes great care to organize the harvested resources according to the Windows Installer's best practices.
 
+:::caution[Licensed feature]
+Like the other features in HeatWave Build Tools, a license file is required to use FireGiant Advanced Harvesting. See the [FireGiant licensing documentation for more information](../firegiant-licensing/).
+:::
+
 Harvesting is controlled by extension elements, `<HarvestProjectOutput/>` and `<HarvestFolder/>`. To get started with Advanced Harvesting add a package reference to the `FireGiant.HeatWave.BuildTools.wixext` extension--via [Manage NuGet Packages][add] in your .wixproj.
 
 The parent element will act as the template for the harvesting. Let's look at a very simple example. Consider a *SetupProject1.wixproj* with a project reference to *ConsoleApplication1.csproj* which in turn has a project reference to *ClassLibrary1.csproj*. In *SetupProject1.wixproj*, list the outputs we want to harvest from the project by adding `HarvestOutputGroup` metadata. In this example, we'll harvest the build outputs and dependencies of *ConsoleApplication1.csproj*:
diff --git a/src/content/docs/heatwave/build-tools/index.md b/src/content/docs/heatwave/build-tools/index.md
@@ -5,7 +5,7 @@ title: About HeatWave Build Tools
 The HeatWave Build Tools extend the WiX Toolset by providing extensions and APIs that improve the development experience of installation packages and bundles.
 
 * [Advanced Harvesting](harvesting/) - the most flexible tooling to gather and organize files from project references and folders.
-* [BundleApplication Framework]() - managed and native libraries to simplify the development of custom Burn-based bootstrapper applications.
+* [Bundle Application Framework]() - managed and native libraries to simplify the development of custom Burn-based bootstrapper applications.
 * [MSIX Extension](msix/) - create MSIX packages from .wxs code.
 * [Driver Extension](driver/) - enhances MSI to install non-PnP, system-level drivers.
 
diff --git a/src/content/docs/heatwave/build-tools/msix/index.md b/src/content/docs/heatwave/build-tools/msix/index.md
@@ -2,7 +2,11 @@
 title: FireGiant MSIX Extension
 description: Documentation how to use the FireGiant MSIX Extension
 sidebar:
-  order: 3
+  order: 0
 ---
 
 The FireGiant MSIX Extension allows you to create MSIX Packages with your existing .wxs source code. Only three additions need to be made to get started. Once complete, building your project will create both an MSI package and an MSIX package.
+
+:::caution[Licensed feature]
+Like the other features in HeatWave Build Tools, a license file is required to use FireGiant MSIX Extension. See the [FireGiant licensing documentation for more information](../firegiant-licensing/).
+:::
diff --git a/src/content/docs/heatwave/build-tools/protected-services.md b/src/content/docs/heatwave/build-tools/protected-services.md
@@ -12,6 +12,10 @@ During installation, the FireGiant protected service extension:
 - Installs the ELAM driver private certificate.
 - Configures the service to launch as a protected service.
 
+:::caution[Licensed feature]
+Like the other features in HeatWave Build Tools, a license file is required to use FireGiant Protected Services Extension. See the [FireGiant licensing documentation for more information](../firegiant-licensing/).
+:::
+
 To use the protected service extension, add a reference to the `FireGiant.HeatWave.BuildTools.wixext` and access the extension by adding the following namespace to your .wxs code:
 
 ```xml title=ProtectedService.wxs
