One approach to solving this could be using the windows-2022image. It seems as if this would also need changes in the build scripts to allow builds on that environment (for example, .NET Framework 4.6.1 SDK is missing there, and the VS version is 2022 and not 2019 that current script expects). Christian and I tried a couple of minor changes, but it seems as if this requires additional investigation.
Please let me know if any additional details are needed here - I will be happy to help!
Context The build agent used in the PR Build/Test pipeline runs Windows Server 10.0.17763. There are some ProjFS APIs that were introduced in later Windows versions, such as 2004. Notably, the symlink API (https://docs.microsoft.com/en-us/windows/win32/api/projectedfslib/ns-projectedfslib-prj_extended_info - 10.0; Build 19041) that was used in https://github.com/microsoft/ProjFS-Managed-API/pull/73.
One approach to solving this could be using the
windows-2022image. It seems as if this would also need changes in the build scripts to allow builds on that environment (for example, .NET Framework 4.6.1 SDK is missing there, and the VS version is 2022 and not 2019 that current script expects). Christian and I tried a couple of minor changes, but it seems as if this requires additional investigation.Please let me know if any additional details are needed here - I will be happy to help!