Pass installer config via template (NAV version fix).

- Solve issue #18 using installer config. template.
- Documentation fix.

Author: Koubek

root/__content/NAV/configs/Install-NavComponentConfig-web.xml renamed to root/__content/NAV/configs/Install-NavComponentConfig-web.tmpl.xml

@@ -14,11 +14,11 @@
   <Component Id="RoleTailoredClient" State="Absent" ShowOptionNode="yes"/>
   <Component Id="ExcelAddin" State="Absent" ShowOptionNode="yes"/>
   <Component Id="ClassicClient" State="Absent" ShowOptionNode="yes"/>
-  <Parameter Id="TargetPath" Value="[WIX_ProgramFilesFolder]\Microsoft Dynamics NAV\100"/>
-  <Parameter Id="TargetPathX64" Value="[WIX_ProgramFilesX64Folder]\Microsoft Dynamics NAV\100"/>
+  <Parameter Id="TargetPath" Value="[WIX_ProgramFilesFolder]\Microsoft Dynamics NAV\[DOCKER.NAV_VERSION]"/>
+  <Parameter Id="TargetPathX64" Value="[WIX_ProgramFilesX64Folder]\Microsoft Dynamics NAV\[DOCKER.NAV_VERSION]"/>
   <Parameter Id="NavServiceSQMOption" Value="false"/>
   <Parameter Id="NavServiceServerName" Value="localhost"/>
-  <Parameter Id="NavServiceInstanceName" Value="SampleDynamicsNAV100"/>
+  <Parameter Id="NavServiceInstanceName" Value="SampleDynamicsNAV[DOCKER.NAV_VERSION]"/>
   <Parameter Id="NavServiceAccount" Value="NT AUTHORITY\NETWORK SERVICE"/>
   <Parameter Id="NavServiceAccountPassword" IsHidden="yes" Value=""/>
   <Parameter Id="NavServiceClientServicesPort" Value="37046"/>

root/__content/NAV/configs/Install-NavComponentConfig.xml renamed to root/__content/NAV/configs/Install-NavComponentConfig.tmpl.xml

@@ -0,0 +1,15 @@
+[CmdletBinding()]
+param (
+    
+    [Parameter(Mandatory=$true)]
+    [String]$NavConfigTmplFullPath,
+
+    [Parameter(Mandatory=$true)]
+    [String]$NavConfigDestFullPath
+
+)
+
+$navVersion = & (Join-Path $PSScriptRoot Get-NavVersionMajor.ps1)
+$navVersion = -join ($navVersion, "0")
+
+(Get-Content $NavConfigTmplFullPath).replace('[DOCKER.NAV_VERSION]', $navVersion) | Set-Content $NavConfigDestFullPath -Force

root/__content/NAV/scripts/Convert-NavInstallConfigTmpl.ps1

@@ -18,6 +18,8 @@ WORKDIR C:\\install\\content
 
 # Add missing registry to be able run main setup.exe (to cheat prerequisite checks).
 RUN powershell c:\install\content\Scripts\Add-MissingRegistry.ps1; \
+    # Set product version (convert installation config file template to the real config file).
+    c:\install\content\Scripts\Convert-NavInstallConfigTmpl.ps1 c:\install\content\configs\Install-NavComponentConfig.tmpl.xml c:\install\content\configs\Install-NavComponentConfig.xml; \
     # Install NAV prerequisites (or at least pretend to), NAV Server and NAV default instance (will be stopped and disabled).
     Import-Module c:\install\content\DynamicsNavDvd\NavInstallationTools.psm1 -Force; \
     Install-NAVComponent -ConfigFile c:\install\content\configs\Install-NavComponentConfig.xml;

root/build/nav/InstallNav.Dockerfile

@@ -14,6 +14,8 @@ WORKDIR C:\\install\\content
 
 # Add missing registry to be able run main setup.exe (to cheat prerequisite checks).
 RUN powershell c:\install\content\Scripts\Add-MissingRegistry.ps1; \
+    # Set product version (convert installation config file template to the real config file).
+    c:\install\content\Scripts\Convert-NavInstallConfigTmpl.ps1 c:\install\content\configs\Install-NavComponentConfig-web.tmpl.xml c:\install\content\configs\Install-NavComponentConfig-web.xml; \
     # Add IIS and related features.
     c:\install\content\Scripts\Install-IIS.ps1; \
     # Install NAV prerequisites (or at least pretend to), NAV Server and NAV default instance (will be stopped and disabled).

root/build/nav/InstallWeb.Dockerfile

@@ -10,6 +10,6 @@ Instantiate independent NAV containers (right now an example with SQL authentica
     * Please, just change all necessary parameters (*-e* values) in the script, eventually, you also change the network driver and remove port mappings etc.
  * `_run.winAuth.ps1`
     * Creates an independent NAV container on the default network (we are considering to be a **nat** network).
-    * This container requires an existing and accessible SQL server instance. The authentication betwen NAV and SQL server will be provided via **Windows Authentication** so you have to create a *Windows login* on the SQL server with *db_owner* privileges on the target database.
+    * This container requires an existing and accessible SQL server instance. The authentication between NAV and SQL server will be provided via **Windows Authentication** so you have to create a *Windows login* on the SQL server with *db_owner* privileges on the target database.
     * NAV user authentication uses **Windows**. This must be properly created in the target database.
     * **This demo requires gMSA to be active and properly configured.**