Change exec to spawn to make CodeQL happy

Author: JustinGrote

test/utils.ts

@@ -6,7 +6,7 @@ import * as vscode from "vscode";
 import { ILogger } from "../src/logging";
 import { IPowerShellExtensionClient } from "../src/features/ExternalApi";
 import { resolveCliArgsFromVSCodeExecutablePath } from "@vscode/test-electron";
-import { execSync, spawnSync } from "child_process";
+import { spawnSync } from "child_process";
 import { existsSync } from "fs";
 
 // This lets us test the rest of our path assumptions against the baseline of
@@ -154,8 +154,17 @@ export async function InstallCSharpExtension() {
 export function BuildBinaryModuleMock() {
     console.log("==BUILDING: Binary Module Mock==");
     const projectPath = path.resolve(`${__dirname}/../../test/mocks/BinaryModule/BinaryModule.csproj`); //Relative to "out/test" when testing.
-    const buildResult = execSync(`dotnet publish ${projectPath}`);
-    console.log(buildResult.toString());
+    const dotnetArgs = [
+        "publish",
+        projectPath
+    ];
+    const buildResult = spawnSync("dotnet", dotnetArgs, {
+        encoding: "utf-8",
+        windowsHide: true
+    });
+    if (buildResult.status !== 0) {
+        throw new Error(`Failed to build binary module mock: ${buildResult.stderr}`);
+    }
 }
 
 /** Waits until the registered vscode event is fired and returns the trigger result of the event.