src/Common.Dotnet.FuzzTest.props

<?xml version="1.0" encoding="utf-8"?>
<!-- Some items may be set in Directory.Build.props in root -->
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <!-- OneFuzz does not currently support testing with .NET 9.
       As a temporary workaround, create a .NET 8 project and use file links 
       to include the code that needs testing. -->
  <PropertyGroup>
    <TargetFramework>net8.0-windows10.0.26100.0</TargetFramework>
  </PropertyGroup>
</Project>
[Infra-BuildScript] Add PowerShell Script to Enforce Shared Common.Dotnet.CsWinRT.props in all CSharp Projects under Src Sub-Folder (#37811) * Add Powershell script to validate whether CSharp project correctly import shared props, update pipeline to enforce such validation, and fixed all projects that didn't import this shared props correctly * add common props for fuzz test project * update the path * Only scans projects in src sub-folder * Update .pipelines/verifyCommonProps.ps1 * Update csproj to include Common.Dotnet.CsWinRT.props * Fix indentation in RegistryPreview.FuzzTests.csproj * exclude TemplateCmdPalExtension.csproj in validation process * exclude TemplateCmdPalExtension.csproj in validation process --------- Co-authored-by: Leilei Zhang <leilzh@microsoft.com> Co-authored-by: Jerry Xu <nxu@microsoft.com> 2025-05-02 20:38:11 -07:00			`<?xml version="1.0" encoding="utf-8"?>`
			`<!-- Some items may be set in Directory.Build.props in root -->`
			`<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">`
			`<!-- OneFuzz does not currently support testing with .NET 9.`
			`As a temporary workaround, create a .NET 8 project and use file links`
			`to include the code that needs testing. -->`
			`<PropertyGroup>`
[Dev][Build] VS 2026 Support (#44304) <!-- Enter a brief description/summary of your PR here. What does it fix/what does it change/how was it tested (even manually, if necessary)? --> ## Summary of the Pull Request This PR updates the PowerToys solution to support Visual Studio 2026 (PlatformToolset v145). It centralizes the build configuration, updates the C++ language standards, and fixes an issue with a MouseJump unit test that appears while using the VS 2026 supported build agent. <!-- Please review the items on the PR checklist before submitting--> ## PR Checklist - [ ] Closes: #xxx - [x] Communication: I've discussed this with core contributors already. If the work hasn't been agreed, this work might be rejected - [x] Tests: Added/updated and all pass - [ ] Localization: All end-user-facing strings can be localized - [x] Dev docs: Added/updated - [ ] New binaries: Added on the required places - [ ] [JSON for signing](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ESRPSigning_core.json) for new binaries - [ ] [WXS for installer](https://github.com/microsoft/PowerToys/blob/main/installer/PowerToysSetup/Product.wxs) for new binaries and localization folder - [ ] [YML for CI pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/ci/templates/build-powertoys-steps.yml) for new test projects - [ ] [YML for signed pipeline](https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml) - [ ] Documentation updated: If checked, please file a pull request on [our docs repo](https://github.com/MicrosoftDocs/windows-uwp/tree/docs/hub/powertoys) and link it here: #xxx <!-- Provide a more detailed description of the PR, other things fixed, or any additional comments/features here --> ## Detailed Description of the Pull Request / Additional comments Build System & Configuration: - Updated `Cpp.Build.props` to use `v145` (VS 2026) as the default `PlatformToolset`, with fall back to `v143` for VS 2022. - Configured C++ Language Standard: - `stdcpplatest` for production projects. - Removed explicit `<PlatformToolset>` definitions from individual project files (approx. 37 modules) to inherit correctly from the central `Cpp.Build.props`. Code Refactoring & Fixes: - Updated `DrawingHelperTests.cs` in MouseJump Unit Test to ease the pixel difference tolerance. This became an issue after switching to the new VS2026 build agent. <!-- Describe how you validated the behavior. Add automated tests wherever possible, but list manual validation steps taken as well --> ## Validation Steps Performed - Validated successful compilation of the entire solution. Similar updates have been made to the .NET 10 branch, but these are much cleaner and will be merged into that branch once fully confirmed working. --------- Co-authored-by: Kai Tao (from Dev Box) <kaitao@microsoft.com> Co-authored-by: Gordon Lam (SH) <yeelam@microsoft.com> 2026-01-28 18:46:34 -05:00			`<TargetFramework>net8.0-windows10.0.26100.0</TargetFramework>`
[Infra-BuildScript] Add PowerShell Script to Enforce Shared Common.Dotnet.CsWinRT.props in all CSharp Projects under Src Sub-Folder (#37811) * Add Powershell script to validate whether CSharp project correctly import shared props, update pipeline to enforce such validation, and fixed all projects that didn't import this shared props correctly * add common props for fuzz test project * update the path * Only scans projects in src sub-folder * Update .pipelines/verifyCommonProps.ps1 * Update csproj to include Common.Dotnet.CsWinRT.props * Fix indentation in RegistryPreview.FuzzTests.csproj * exclude TemplateCmdPalExtension.csproj in validation process * exclude TemplateCmdPalExtension.csproj in validation process --------- Co-authored-by: Leilei Zhang <leilzh@microsoft.com> Co-authored-by: Jerry Xu <nxu@microsoft.com> 2025-05-02 20:38:11 -07:00			`</PropertyGroup>`
			`</Project>`