replacing the setVersionNr script

Author: Bettina Heim

build/bootstrap.cmd

@@ -6,7 +6,7 @@ dotnet  --info || GOTO missingDotnet
 git --version  || GOTO missingGit
 
 :: Set Build number on all files that uses it
-CALL build\setVersionNumber.cmd
+call powershell -NoProfile build\setVersionNumber.ps1
 
 :: Initialize the compiler's nuspec file
 CALL :nuspecBootstrap

build/setVersionNumber.cmd

@@ -0,0 +1,34 @@
+param(
+    [string]
+    $AssemblyVersion = $Env:ASSEMBLY_VERSION,
+
+    [string]
+    $NuGetVersion = $Env:NUGET_VERSION
+);
+
+if ("$AssemblyVersion".Trim().Length -eq 0) {
+    $Date = Get-Date;
+    $Year = $Date.Year.ToString().Substring(2);
+    $Month = $Date.Month.ToString().PadLeft(2, "0");
+    $Hour   = (Get-Date).Hour.ToString().PadLeft(2, "0");
+    $Minute   = (Get-Date).Minute.ToString().PadLeft(2, "0");
+    $AssemblyVersion = "0.0.$Year$Month.$Hour$Minute";
+}
+
+if ("$NuGetVersion".Trim().Length -eq 0) {
+    $NuGetVersion = "$AssemblyVersion-alpha";
+}
+
+Get-ChildItem -Recurse *.v.template `
+    | ForEach-Object {
+        $Source = $_.FullName;
+        $Target = $Source.Substring(0, $Source.Length - 11);
+        Write-Verbose "Replacing ASSEMBLY_VERSION with $AssemblyVersion in $Source and writing to $Target.";
+        Get-Content $Source `
+            | ForEach-Object {
+                $_.
+                    Replace("#ASSEMBLY_VERSION#", $AssemblyVersion).
+                    Replace("#NUGET_VERSION#", $NuGetVersion)
+            } `
+            | Set-Content $Target -NoNewline
+    }

build/setVersionNumer.ps1

@@ -69,5 +69,5 @@ Change back to the "Extension" debugger and resume.
 ### semver Issues ###
 
 You may see an error when packaging or debugging the VS Code extension indicating that the package is not semver compatible.
-This indicates that the build script `setVersionNumber.cmd` did not produce a SemVer 2.0–compatible version number when writing `package.json` from `package.json.v.template`, typically due to a mis-set environment variable.
-If this happens, correct the environment variables used by `setVersionNumber.cmd` or manually edit the `version` property of `package.json` (note that any such manual edits **will** be overwritten by calls to `setVersionNumber.cmd` and will not be saved in the repo).
+This indicates that the build script `setVersionNumber.ps1` did not produce a SemVer 2.0–compatible version number when writing `package.json` from `package.json.v.template`, typically due to a mis-set environment variable.
+If this happens, correct the environment variables used by `setVersionNumber.ps1` or manually edit the `version` property of `package.json` (note that any such manual edits **will** be overwritten by calls to `setVersionNumber.ps1` and will not be saved in the repo).