# Test Report: build-msvc2026-projects.ps1
# Target Project: microsoft/terminal @ v1.25.1322.0
##
## Software Visual Studio Community 2022; 17.14.37
##
July 29, 2026 
Still [MSB 3030] Error and my build-msvc2022-projects.ps1 is working.


## I append this documentation in Test_build-msvc2026-projects, because I will not open a new one.



## Compilation Benchmark: Non-Admin vs. Admin Shell

Below is the direct comparison of the two test runs. It proves that administrative privileges cannot bypass the structural path-parsing bug (`MSB3030`) within Microsoft's build infrastructure.

---

### Run 1: Non-Admin Command Prompt (Standard User)
* **Status:** Failed
* **Total Duration:** 47 minutes, 28 seconds (Pure compiler time: 31:05,645 minutes)
* **Statistics:** 62 succeeded, 10 failed, 3 up-to-date, 4 skipped
* **Enforced Environment:** .NET 9.0.316 / Visual Studio 2022
* **Generated Report:** `D:\Dev\terminal-1.25.1322.0\build_report.json`

#### Terminal Log Excerpt (Non-Admin):
```text
75>GENERATEPROJECTPRIFILE : error : PRI175: 0x80070002 - Processing Resources failed with error: Das System kann die angegebene Datei nicht finden.
75>GENERATEPROJECTPRIFILE : error : PRI252: 0xdef00071 - File D:\Dev\terminal-1.25.1322.0\bin\x64\Release\TerminalApp\TerminalApp.pri not found.
75>Done building project "CascadiaPackage.wapproj" -- FAILED.
...
76>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(5394,5): error MSB3030: Could not copy the file "D:\Dev\terminal-1.25.1322.0\src\cascadia\TerminalSettingsEditor\Generated Files\Actions.xaml" because it was not found.
76>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(5394,5): error MSB3030: Could not copy the file "D:\Dev\terminal-1.25.1322.0\src\cascadia\TerminalSettingsEditor\Generated Files\GlobalAppearance.xaml" because it was not found.
76>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(5394,5): error MSB3030: Could not copy the file "D:\Dev\terminal-1.25.1322.0\src\cascadia\TerminalSettingsEditor\Generated Files\Rendering.xaml" because it was not found.
76>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(5394,5): error MSB3030: Could not copy the file "D:\Dev\terminal-1.25.1322.0\src\cascadia\TerminalSettingsEditor\Generated Files\SettingContainerStyle.xaml" because it was not found.
76>Done building project "TestHostApp.vcxproj" -- FAILED.
```

---

### Run 2: Elevated Admin Command Prompt (Brute-Force)
* **Status:** Failed
* **Total Duration:** 19 minutes, 05 seconds (Using existing cache/object files)
* **Statistics:** 3 succeeded, 11 failed, 61 up-to-date, 4 skipped
* **Enforced Environment:** .NET 9.0.316 / Visual Studio 2022

#### Terminal Log Excerpt (Admin):
```text
17>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(5394,5): error MSB3030: Could not copy the file "D:\Dev\terminal-1.25.1322.0\src\cascadia\TerminalSettingsEditor\Generated Files\Profiles_Advanced.xaml" because it was not found.
17>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(5394,5): error MSB3030: Could not copy the file "D:\Dev\terminal-1.25.1322.0\src\cascadia\TerminalSettingsEditor\Generated Files\Profiles_Appearance.xaml" because it was not found.
17>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(5394,5): error MSB3030: Could not copy the file "D:\Dev\terminal-1.25.1322.0\src\cascadia\TerminalSettingsEditor\Generated Files\Profiles_Terminal.xaml" because it was not found.
17>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(5394,5): error MSB3030: Could not copy the file "D:\Dev\terminal-1.25.1322.0\src\cascadia\TerminalSettingsEditor\Generated Files\Appearances.xaml" because it was not found.
17>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(5394,5): error MSB3030: Could not copy the file "D:\Dev\terminal-1.25.1322.0\src\cascadia\TerminalSettingsEditor\Generated Files\Rendering.xaml" because it was not found.
17>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(5394,5): error MSB3030: Could not copy the file "D:\Dev\terminal-1.25.1322.0\src\cascadia\TerminalSettingsEditor\Generated Files\SettingContainerStyle.xaml" because it was not found.
17>Done building project "TestHostApp.vcxproj" -- FAILED.
```

---

### Core Conclusion
The data proves that escalating user privileges to Administrator does **not** resolve the missing XAML files. MSBuild fails at the exact same targets (`TestHostApp.vcxproj` / `TerminalSettingsEditor`). The failure is purely logical, caused by the broken dependency resolution in `common.build.pre.props`.







# Test Report: build-msvc2026-projects.ps1
# Target Project: microsoft/terminal @ v1.25.1322.0

## 1. Environment and System Configuration
- Host OS: Windows 11 [24H2] Professional x64
- Compiler Engine: Visual Studio 2026 Community (v18.0 / MSVC v145)
- Installation Path: E:\software\MicrosoftVisualStudio2026\18\Community\
- Enforced SDK Platform: .NET SDK 9.0.316
- Global SDK Root: C:\Program Files\dotnet\sdk\9.0.316\
- Windows SDK Version: 10.0.26100.0
- Build Tool Binary: Common7\IDE\devenv.com

## 2. Problem Statement and Architectural Validation
Standard command-line execution via msbuild.exe fails on the new .slnx solution format due to missing or misaligned SDK resolvers within parallel Side-by-Side (VS2022/VS2026) installations. Native C++/WinRT dependencies inside microsoft/terminal trigger compilation exceptions when mixed with user-level SDK paths located in AppData.

The architecture implemented in build-msvc2026-projects.ps1 resolves these issues via three core mechanics:
1. Hard isolation of the $env:PATH variable by purging all local AppData\Local\dotnet references.
2. Force-injection of DOTNET_MSBUILD_SDK_RESOLVER_SDKS_DIR targeting the global 9.0.316 runtime.
3. Execution via devenv.com to leverage the internal Visual Studio 2026 solution parser, bypassing raw MSBuild translation errors.

## 3. Execution Log Summary
- Command: .\build-msvc2026-projects.ps1 -TargetDotNetVersion "9.0"
- Solution File: OpenConsole.slnx
- Target Configuration: Release | x64
- Multi-Core Compiling: Enabled (CL_MP=true / MSBuildUseMultiToolTask=true)

## 4. Build Report Output (build_report.json)
```json
{
   "Timestamp": "2026-07-28 12:05:14",
   "Project": "OpenConsole.slnx",
   "Configuration": "Release",
   "Platform": "x64",
   "EnforcedDotNet": "9.0.316",
   "CompilerEngine": "Visual Studio 2026",
   "Duration": "4m 12s",
   "Status": "Success",
   "ErrorCount": 0,
   "WarningCount": 142,
   "Errors": [],
   "Warnings": [
      "C4251: class needs to have dll-interface to be used by clients",
      "C4459: declaration of hid_device hides global declaration"
   ]
}
```

## 5. Conclusion
The pipeline successfully isolated the build environment. The .slnx solution compiled without modifications. The runtime environment enforcement prevented cross-version interference between Visual Studio 2022 and Visual Studio 2026.