| 14 Aug 2025 |
 oatmealraisin | Idk if I can replicate at this point, a lot has changed | 22:12:52 |
 Corngood | Well in that case the projectFile would just be `API.csproj`, or you could probably just omit it. | 22:13:37 |
| oatmealraisin | Yes, but projectReferences would be missing, I don't have error logs but it would complain about the csproj files for project references being missing | 22:15:49 |
| oatmealraisin | It's very possible I was doing something else wrong, but now all the nix stuff is in a different directory | 22:20:04 |
| Corngood | Yeah, you can't do it with ProjectReference. You need to use PackageReference. There are basically two ways to do what you're trying to do, and you're sort of in-between them:
-
one nix derivation with an assortment of projects linked together with ProjectReference, one deps.json
-
one nix derivation per nuget package with packNupkg = true, using PackageReference
| 22:24:38 |
 GGG | by default it just copies all json files to publish output | 22:47:48 |
| GGG | (I can't remember if it's ASP.NET Core specific or not) | 22:47:59 |
| 15 Aug 2025 |
 Emma [it/its] | huh? i've never had aspnetcore do that | 12:55:48 |
| Emma [it/its] | it sure doesnt copy appsettings.Local.json | 12:56:14 |
| Emma [it/its] | * it sure doesnt copy appsettings.Local.json by default | 12:56:18 |
