microsoft · brianrob · May 27, 2026 · May 27, 2026
@@ -7,11 +7,8 @@ pr:
 jobs:
   - job: PerfView_Debug
     pool:
-      vmImage: 'windows-2022'
+      vmImage: 'windows-2025-vs2026'
       name: Azure Pipelines
-      demands:
-      - msbuild
-      - vstest
 
     steps:
     - template: /.pipelines/perfview-job.yml
@@ -28,11 +25,8 @@ jobs:
 
   - job: PerfView_Release
     pool:
-      vmImage: 'windows-2022'
+      vmImage: 'windows-2025-vs2026'
       name: Azure Pipelines
-      demands:
-      - msbuild
-      - vstest
 
     steps:
     - template: /.pipelines/perfview-job.yml

@@ -303,7 +303,7 @@ After scoring myself on the rubric:
 ## Repository-Specific Knowledge
 
 ### Build System
-- **Full solution** (Windows only): `PerfView.sln` - requires Visual Studio 2022
+- **Full solution** (Windows only): `PerfView.sln` - requires Visual Studio 2026 with the repository `.vsconfig` components installed. Native ETWClrProfiler projects use the latest installed MSVC v145 toolset.
 - **Individual projects** (Linux compatible via dotnet CLI):
   - TraceEvent: `dotnet build src/TraceEvent/TraceEvent.csproj`
   - FastSerialization: `dotnet build src/FastSerialization/FastSerialization.csproj`

@@ -17,7 +17,7 @@ PerfView is a Windows performance-analysis tool for investigating CPU and memory
 
 ## Build & Test
 
-- **Full solution (Windows):** `build.cmd` or open `PerfView.sln` in Visual Studio 2022+ and build.
+- **Full solution (Windows):** `build.cmd` or open `PerfView.sln` in Visual Studio 2026 with the repository `.vsconfig` components installed. Native ETWClrProfiler projects use the latest installed MSVC v145 toolset.
 - **Individual projects (cross-platform via dotnet CLI):**
   - `dotnet build src/TraceEvent/TraceEvent.csproj -c Debug`
   - `dotnet build src/FastSerialization/FastSerialization.csproj -c Debug`

@@ -16,6 +16,13 @@ steps:
     msbuildArguments: '/restore'
     configuration: ${{ parameters.flavor }}
 
+- task: VisualStudioTestPlatformInstaller@1
+  displayName: 'Install VS Test'
+  inputs:
+    versionSelector: 'latestStable'
+    packageFeedSelector: 'customFeed'
+    customFeed: 'https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public/nuget/v3/index.json'
+
 - task: VSTest@2
   displayName: 'Run Tests'
   inputs:
@@ -27,6 +34,7 @@ steps:
       **\bin\**\PerfViewTests.dll
       **\bin\**\TraceParserGen.Tests.dll
     testRunTitle: 'PerfView - ${{ parameters.flavor }}'
+    vsTestVersion: 'toolsInstaller'
     runTestsInIsolation: true
     otherConsoleOptions: '--blame'
 

@@ -54,36 +54,38 @@ you can do that by following the rest of these instructions.
 
 ### Tools Needed to Build PerfView
 
-The only tool you need to build PerfView is Visual Studio 2022.  The [Visual Studio 2022 Community Edition](https://www.visualstudio.com/vs/community/) 
+The only tool you need to build PerfView is Visual Studio 2026.  The [Visual Studio Community Edition](https://www.visualstudio.com/vs/community/)
 can be downloaded *for free* and has everything you need to fetch PerfView from GitHub, build and test it. We expect you 
-to download Visual Studio 2022 Community Edition if you don't already have Visual Studio 2022.
+to download Visual Studio Community Edition if you don't already have Visual Studio 2026.
 
 In your installation of Visual Studio, you need to ensure you have the following workloads and components installed:
 
   * **.NET desktop development** workload with all default components.
   * **Desktop development with C++** workload with all default components plus the latest Windows 10 SDK.
     * The Windows 10 SDK is not enabled by default in this workload, so you will need to check the box for it to be installed.
-  * **MSVC v143 - VS 2022 C++ x64/x86 Spectre-mitigated libs (Latest)** component.
+  * **MSVC v145 - VS 2026 C++ x64/x86 build tools (Latest)** component.
+  * **MSVC v145 - VS 2026 C++ x64/x86 Spectre-mitigated libs (Latest)** component.
     * This can be found under the 'Individual Components' tab.
 
 A `.vsconfig` file is included in the root of the repository that can be used to install the necessary components. When 
 opening the solution in Visual Studio, it will prompt you to install any components that it thinks are missing from your 
-installation.  Alternatively, you can [import the `.vsconfig` in the Visual Studio Installer](https://learn.microsoft.com/en-us/visualstudio/install/import-export-installation-configurations?view=vs-2022#import-a-configuration).
+installation.  Alternatively, you can [import the `.vsconfig` in the Visual Studio Installer](https://learn.microsoft.com/en-us/visualstudio/install/import-export-installation-configurations#import-a-configuration).
+PerfView intentionally uses the latest installed MSVC v145 toolset from Visual Studio 2026.
 
-If you get any errors compiling the ETWClrCompiler projects, it is likely because you either don't have the Windows 10 SDK 
+If you get any errors compiling the ETWClrProfiler projects, it is likely because you either don't have the Windows 10 SDK
 installed, or you don't have the spectre-mitigated libs installed. Please refer to the [troubleshooting section](#information-for-build-troubleshooting) for more information.
 
 
 ### Cloning the PerfView GitHub Repository. 
 
 The first step in getting started with the PerfView source code is to clone the PerfView GitHub repository.
-If you are already familiar with how GIT, GitHub, and Visual Studio 2022 GIT support works, then you can skip this section.
-However, if not, the [Setting up a Local GitHub repository with Visual Studio 2022](documentation/SettingUpRepoInVS.md) document
-will lead you through the basics of doing this. All it assumes is that you have Visual Studio 2022 installed.
+If you are already familiar with how GIT, GitHub, and Visual Studio 2026 GIT support works, then you can skip this section.
+However, if not, the [Setting up a Local GitHub repository with Visual Studio 2026](documentation/SettingUpRepoInVS.md) document
+will lead you through the basics of doing this. All it assumes is that you have Visual Studio 2026 installed.
 
 ### How to Build and Debug PerfView 
 
-PerfView is developed in Visual Studio 2022 using features through C# 7.3.
+PerfView is developed in Visual Studio 2026 using features through C# 7.3.
 
   * The solution file is PerfView.sln.  Opening this file in Visual Studio (or double clicking on it in 
   the Windows Explorer) and selecting Build -> Build Solution, will build it. You can also build the 
@@ -117,16 +119,16 @@ among other things a PerfView.exe.   This one file is all you need to deploy.
   explicit 'scope') and needs to refer to PerfView to resolve some of its references.   Thus you will get many 'not found'
   issues in the 'Global' project.  These can be ignored until you get every other part of the build working.
 
-  * One of the invariants of the repo is that if you are running Visual Studio 2022 and you simply sync and build the
+  * One of the invariants of the repo is that if you are running Visual Studio 2026 and you simply sync and build the
   PerfView.sln file, it is supposed to 'just work'.   If that does not happen, and the advice above does not help, then
   we need to either fix the repo or update the advice above. Thus it is reasonable to open a GitHub issue. If you
   do this, the goal is to fix the problem, which means you have to put enough information into the issue to do that.
   This includes exactly what you tried, and what the error messages were.
 
-  * You can also build PerfView from the command line (but you still need Visual Studio 2022 installed).   It is a two step process.
+  * You can also build PerfView from the command line (but you still need Visual Studio 2026 installed).   It is a two step process.
   First you must restore all the needed nuget packages, then you do the build itself. To do this:
     1. Open a developer command prompt.  You can do this by hitting the windows key (by the space bar) and type
-       'Developer command prompt'.  You should see a entry for this that you can select (if Visual Studio 2022 is installed).
+       'Developer command prompt'.  You should see a entry for this that you can select (if Visual Studio 2026 is installed).
     2. Change directory to the base of your PerfView source tree (where PerfView.sln lives). 
     3. Restore the nuget packages by typing the command 'msbuild /t:restore'
     4. Build perfView by typing the command 'msbuild'
@@ -135,8 +137,10 @@ among other things a PerfView.exe.   This one file is all you need to deploy.
   frankly any error associated with building the ETWClrProfiler dlls, you should make sure that you have the Windows 10 SDK installed.  Unfortunately this library tends not to be 
   installed with Visual Studio anymore unless you ask for it explicitly.   To fix it launch the Visual Studio Installer, modify the installation, and then look under the C++ Desktop Development and check that the Windows SDK 10.0.17763.0 option is selected.  If not, select it and continue.  Then try building PerfView again.
 
-  * If you get an error "MSB8040: Spectre-mitigated libraries are required for this project",  modify your Visual Studio 
-    installation to ensure that you have the 'MSVC v143 - VS 2022 C++ x64/x86 Spectre-mitigated libs (Latest)' component installed. 
+  * If you get an error "MSB8040: Spectre-mitigated libraries are required for this project",  modify your Visual Studio
+    installation to ensure that you have the 'MSVC v145 - VS 2026 C++ x64/x86 Spectre-mitigated libs (Latest)' component installed.
+
+  * If you get an error that the v145 platform toolset is not found, import the repository `.vsconfig` file in the Visual Studio Installer or install the Visual Studio 2026 C++ desktop workload.
 
 
 ### Running Tests

@@ -1,13 +1,13 @@
-# GitHub Repository Setup with Visual Studio 2019
+# GitHub Repository Setup with Visual Studio 2026
 
 This section tells you how to build a project that is already hosted on GitHub, 
-using Visual Studio 2019. If you don't already have Visual Studio 2019, you 
+using Visual Studio 2026. If you don't already have Visual Studio 2026, you
 can get the community edition for free from 
 [this link](https://www.visualstudio.com/vs/community/).
 This section also goes through important routine tasks like getting the latest 
 changes from GitHub and submitting a pull request to the main branch.
 
-It will show you how to do this using just Visual Studio 2019. Older versions 
+It will show you how to do this using just Visual Studio 2026. Older versions
 of Visual Studio as well as other IDEs are possible, but not covered here.  
 You can also use 'raw' git commands but I don't cover that here.  
 

@@ -1,9 +1,9 @@
-# Setting Up *Without* a Fork with Visual Studio 2019
+# Setting Up *Without* a Fork with Visual Studio 2026
 
  * See also [Setting up a Repo in VS](SettingUpRepoInVS.md) for important background material. 
  * See also [Open Source GitHub Setup and Workflow](OpenSourceGitWorkflow.md) for the setup needed for pull requests.  
 
-Here we describe how to use Visual Studio 2019 to set a local build of the GitHub project https://github.com/Microsoft/perfview.   
+Here we describe how to use Visual Studio 2026 to set a local build of the GitHub project https://github.com/Microsoft/perfview.
 Because this project is open source, anyone can read it so this works even if you don't have a GitHub account, but
 of course you will only have read-only access.   
 
@@ -147,4 +147,3 @@ At this point we have described the critical workflows
 
 
 
-
@@ -29,8 +29,8 @@
     <SpectreMitigation>Spectre</SpectreMitigation>
   </PropertyGroup>
   <PropertyGroup>
-    <PlatformToolset>v143</PlatformToolset>
-    <PlatformToolsetVersion>143</PlatformToolsetVersion>
+    <PlatformToolset>v145</PlatformToolset>
+    <PlatformToolsetVersion>145</PlatformToolsetVersion>
   </PropertyGroup>
   <Import Project="$(VCTargetsPath)\Microsoft.Cpp.props" />
   <ImportGroup Label="ExtensionSettings">

@@ -29,8 +29,8 @@
     <SpectreMitigation>Spectre</SpectreMitigation>
   </PropertyGroup>
   <PropertyGroup>
-    <PlatformToolset>v143</PlatformToolset>
-    <PlatformToolsetVersion>143</PlatformToolsetVersion>
+    <PlatformToolset>v145</PlatformToolset>
+    <PlatformToolsetVersion>145</PlatformToolsetVersion>
   </PropertyGroup>
   <Import Project="$(VCTargetsPath)\Microsoft.Cpp.props" />
   <ImportGroup Label="ExtensionSettings">