Nix + dotnet | 120 Members | |
| 23 Servers |
| Sender | Message | Time |
|---|---|---|
| 27 May 2025 | ||
| 19:17:22 | ||
| 28 May 2025 | ||
| 15:18:28 | ||
| 15:21:57 | ||
| 29 May 2025 | ||
| Hey, I'm here again to cause issues. :P
| 02:14:32 | |
| Does anyone happen to have any ideas? | 02:14:42 | |
Oh maybe that's my fault for not fully fixing the for project in... section - Lemme see if I can fix it. | 02:16:44 | |
| Yep, silly me - That was it. | 02:17:23 | |
| Now I'm running into NETSDK1004 so that's definitely progress! | 02:38:00 | |
| You might want to look at
| 11:59:28 | |
Thanks for the suggestion! I already am looking at Avalonia and had originally copied runtimeIds and configurePhase without modification, which caused the initial MSB1009 issue that I was getting. Removing the project for loop fixed that, as I only have the one project file. Unfortunately for me, there's no listed fix for NETSDK1004 in the Avalonia package.nix | 13:11:47 | |
* Thanks for the suggestion! I already am looking at Avalonia and had originally copied runtimeIds and configurePhase without modification, which caused the initial MSB1009 issue that I was getting. Removing the project for loop fixed that, as I only have the one project file. Unfortunately for me, there's no listed fix for NETSDK1004 in the Avalonia package.nix. | 13:11:59 | |
| (Or in all of Nixpkgs from what I can tell. I'm not terribly surprised at that, though I was a little hopeful.) | 13:18:44 | |
| I think NETSDK1004 would usually be caused by restore/build not using the same args, or possibly a mismatch between restoring a project and a solution? | 13:34:01 | |