Simple vcpkg script

Author: florelis

azure-pipelines.yml

@@ -84,9 +84,9 @@ jobs:
       nugetConfigPath: '$(nugetConfig)'
 
   - task: PowerShell@2
-    displayName: Find and Integrate Vcpkg
+    displayName: Initialize Vcpkg
     inputs:
-      filePath: 'templates\Find-AndIntegrate-Vcpkg.ps1'
+      filePath: 'tools\Initialize-Vcpkg.ps1'
 
   - task: VSBuild@1
     displayName: Build Fuzzing Artifacts

doc/Developing.md

@@ -32,7 +32,9 @@ For naming, formatting, error handling, casts, `std::move()` usage, and resource
    - For VS Community: `winget configure .config/configuration.winget`
    - For VS Professional: `winget configure .config/configuration.vsProfessional.winget`
    - For VS Enterprise: `winget configure .config/configuration.vsEnterprise.winget`
-3. Run `vcpkg integrate install` from the Developer Command Prompt / Developer PowerShell for VS. This is a one-time setup step until the configuration file in step 2 is updated to work with vcpkg setup.
+3. From PowerShell at the repository root, run [`.\tools\Initialize-Vcpkg.ps1`](../tools/Initialize-Vcpkg.ps1) to enable MSBuild integration with Visual Studio's bundled vcpkg.
+   This replaces any existing vcpkg integration for the current user.
+   This is a one-time setup step until the configuration file in step 2 is updated to work with vcpkg setup.
 
 Open `winget-cli\src\AppInstallerCLI.sln` in Visual Studio and build. We currently only build using the solution; command-line methods of building a VS solution should work as well.
 

templates/Find-AndIntegrate-Vcpkg.ps1

@@ -81,8 +81,10 @@ is neither a parameter nor a path in this directory.
 **Pipeline variables.** None. `jobs-build.yml` sets what it needs at job scope — `solution`, so it
 can be rooted, and `EnableDetectorVcpkg`, so Component Governance detects the vcpkg dependencies.
 
-**A Windows agent** with Visual Studio 2022 and vcpkg. **The `Test` and `BuildPowerShellModule` jobs need
-more than the `Build` job does — see "Agent requirements" below.**
+**A Windows agent** with Visual Studio 2022 or newer and its vcpkg component installed. The `Build` job
+runs [tools\Initialize-Vcpkg.ps1](../tools/Initialize-Vcpkg.ps1) to enable user-wide MSBuild integration
+with Visual Studio's bundled vcpkg.
+**The `Test` and `BuildPowerShellModule` jobs need more than the `Build` job does — see "Agent requirements" below.**
 
 **Outbound network access.** The test jobs reach several public endpoints, which is worth checking
 before wiring this up on a restricted network:

templates/README.md

@@ -120,9 +120,9 @@ jobs:
       nugetConfigPath: '$(nugetConfig)'
 
   - task: PowerShell@2
-    displayName: Find and Integrate Vcpkg
+    displayName: Initialize Vcpkg
     inputs:
-      filePath: '${{ parameters.sourceRoot }}\templates\Find-AndIntegrate-Vcpkg.ps1'
+      filePath: '${{ parameters.sourceRoot }}\tools\Initialize-Vcpkg.ps1'
 
   - ${{ if ne(parameters.releaseTagJob, '') }}:
     - task: PowerShell@2

templates/jobs-build.yml

@@ -0,0 +1,32 @@
+<#
+.SYNOPSIS
+    Enables user-wide MSBuild integration for Visual Studio's bundled vcpkg.
+#>
+
+$ErrorActionPreference = 'Stop'
+
+$vswhere = "${env:ProgramFiles(x86)}\Microsoft Visual Studio\Installer\vswhere.exe"
+if (-not (Test-Path -LiteralPath $vswhere -PathType Leaf))
+{
+    throw "vswhere.exe not found at $vswhere."
+}
+
+$vcpkg = & $vswhere -latest -products '*' `
+    -requires Microsoft.VisualStudio.Component.Vcpkg `
+    -find 'VC\vcpkg\vcpkg.exe'
+if ($LASTEXITCODE -ne 0)
+{
+    throw "vswhere.exe failed with exit code $LASTEXITCODE."
+}
+
+if (-not $vcpkg -or -not (Test-Path -LiteralPath $vcpkg -PathType Leaf))
+{
+    throw 'No Visual Studio installation with vcpkg.exe found.'
+}
+
+Write-Host "Running: `"$vcpkg`" integrate install"
+& $vcpkg integrate install
+if ($LASTEXITCODE -ne 0)
+{
+    throw "vcpkg integrate install failed with exit code $LASTEXITCODE."
+}