Conversation
…itching all test projects to net11)
|
@Youssef1313 If I may pester you for a second - https://github.com/icsharpcode/ILSpy/actions/runs/23659269195/job/68924889813#step:14:141 there MTP (I guess) complains about the runtime not being there The third test project works although it targets net10-windows as well... expected behavior, what to change, if bug - where to report properly? |
|
Looks like all is green now? |
|
@Youssef1313 Only because I switched the projects to net11 (40f4489). |
|
Generally speaking, if you want the test project to target net10 while you use .NET 11 SDK, then you need to install the .NET 10 runtime as well (not necessarily install the .NET 10 SDK - just the runtime). |
|
I started out with the 2025 image and VS2022 on it, and ran into problems with msbuild (but we use that image with our vCurrent builds that target net10 and use MTP). Then I switched over to 2025-vs2026 which has the following software installed https://github.com/actions/runner-images/blob/main/images/windows/Windows2025-VS2026-Readme.md, which includes Microsoft.WindowsDesktop.App: 8.0.6, 8.0.22, 8.0.25, 9.0.6, 9.0.14, 10.0.5. That should have done the trick and lines up with the error message I tagged you with ("10.0.0 needed, 10.0.5 found") The only thing I can think of that might throw off MTP is our use of DOTNET_ROOT, see ILSpy/.github/workflows/build-ilspy.yml Line 41 in a467610 |
|
That use of DOTNET_ROOT might be the cause indeed. |
Built with preview 2 https://dotnet.microsoft.com/en-us/download/dotnet/11.0
To use the transport feed:
<package pattern="Microsoft.CodeAnalysis.*" />to dotnet-toolsProblem: MTP for UseWpf directly/indirectly tests. Solution: switch all test projects to net11.
Problem: msbuild-related test failures. Solution: switch to runner image with VS2026 (Same issue as the usage of msbuild in the pipeline).
Problem: msbuild in the Windows pipeline was acting up, so I had to replace it with dotnet build. Action error for documentation: