C
C#3mo ago
Brady Kelly

Project skipped on Solution Build

My solution of five projects has Cts.Maui.Dx as the main project, with a project reference to Cts.Maui.Models, but when I try a solution build in Rider, I get the following build output, with errors because Cts.Maui.Models is missing. The other two projects seem to be building fine.
Build with surface heuristics started at 08:16:46
Use build tool: C:\Program Files\dotnet\sdk\8.0.204\MSBuild.dll
CONSOLE: MSBuild version 17.9.8+b34f75857 for .NET
CONSOLE: Build started 4/21/2024 8:16:46 AM.
CONSOLE: Project "C:\Users\brady\AppData\Local\Temp\Zojapov.proj" on node 1 (default targets).
CONSOLE: ControllerTarget:
CONSOLE: Run controller from C:\Program Files\JetBrains\Rider\r2r\2023.3.4R\533CB127EA8D8D4CE2837F707AB6B81\JetBrains.Platform.MsBuildTask.v17.dll
0>------- Started building project: Cts.Wpf
1>------- Started building project: Cts.Maui.Tests
2>------- Started building project: Cts.Maui.Dx
Build with surface heuristics started at 08:16:46
Use build tool: C:\Program Files\dotnet\sdk\8.0.204\MSBuild.dll
CONSOLE: MSBuild version 17.9.8+b34f75857 for .NET
CONSOLE: Build started 4/21/2024 8:16:46 AM.
CONSOLE: Project "C:\Users\brady\AppData\Local\Temp\Zojapov.proj" on node 1 (default targets).
CONSOLE: ControllerTarget:
CONSOLE: Run controller from C:\Program Files\JetBrains\Rider\r2r\2023.3.4R\533CB127EA8D8D4CE2837F707AB6B81\JetBrains.Platform.MsBuildTask.v17.dll
0>------- Started building project: Cts.Wpf
1>------- Started building project: Cts.Maui.Tests
2>------- Started building project: Cts.Maui.Dx
This is the abridged output. The actual output has three bloody entries for dotnet.exe exec "C:\Program Files\dotnet\sdk\8.0.204\Roslyn\bincore\csc.dll" that total a whopping 15kb per line but I assume these are for the three projects that are building.
1 Reply
Brady Kelly
Brady Kelly3mo ago
Oh, sorry, I forgot to include them in the copy-paste. I moved the library classes back into the main project to work around that, and now if I add the library project back it builds this time, for Android and iOS targets. Although I think the main problem is that the errors were caused by the class library not building and that output being missing to the main project build. There was an error for Android and for iOS about the metadata file not being found. The classic error when a missing assembly is referenced. My question here was why was the library not building. That was what seemed to be cause of the errors. Yes, it was, I'm think I would have got errors trying to use the types it exposes even before doing a solution build if it wasn't.