Nix + dotnet | 123 Members | |
| 23 Servers |
| Sender | Message | Time |
|---|---|---|
| 9 Aug 2025 | ||
| unless if homedir workload installation got re-enabled recently | 01:23:09 | |
I'm also getting this error intermittently, error MSB4018: System.IO.IOException: The process cannot access the file '/build/y0lpd34wqi3vwms9ci0i5yq4mq90sz23-source/src/Infrastructure/bin/Release/net8.0/Infrastructure.deps.json' because it is being used by another process. | 01:24:11 | |
| Not sure what to make of that | 01:24:16 | |
| ngl I do not know what this means | 01:24:30 | |
In reply to @oatmealraisin:matrix.orgI think that's usually if you're building a solution file with concurrency. | 01:29:24 | |
| Is concurrency on by default? | 01:30:20 | |
| Yeah, unless `enableParallelBuilding = false`. There's documentation somewhere about why that's not safe in all cases, but I haven't found it yet... | 01:32:38 | |
| I must've glanced over it too fast, I thought it was off by default. I'll change that. I'm also not making derivations for every projectreference yet.. | 01:34:36 | |
| Hey! The whole thing just built | 01:35:15 | |
| It doesn't run because it needs selfContainedBuild but just getting to this point is great. Corngood thanks again for the help | 01:59:20 | |
In reply to @oatmealraisin:matrix.org stdenv is off by default, buildDotnetModule is on by default... I think some other languages did the same because they don't have the legacy of stdenv. The documentation I was talking about was the concurrent solution building problem, but that's an upstream dotnet thing. | 02:04:20 | |
| For some reason I can't find any reference now, but I seem to remember the problem was with solution files specifically causing the same project to be build twice concurrently when there's a diamond dependency. I think it had something to do with the target framework or runtime being used as well. There are a bunch of packages that work around it. For example
| 02:19:29 | |
| 13 Aug 2025 | ||
| Hi, me again. Sorry
Anyone have any suggestions on what to do next? | 17:18:25 | |
| i thought nativeaot and multi-file were mutually exclusive? | 17:19:34 | |
| Can't say I kno | 17:19:56 | |
| * Can't say I know | 17:19:58 | |
| nativeaot has to be self-contained, yeah | 17:20:22 | |
| ready2run is a form of aot, but that's not nativeaot | 17:20:55 | |
My friend seems to think that AoT (I'm assuming nativeaot) can be enabled while selfContained = false; is set (seemingly to not need the runtime at all?), but the above error seems to claim otherwise. | 17:29:43 | |
Admittedly I'm not quite sure what I'm asking, since the build works fine with dotnetInstallFlags = [ "-p:PublishAot=false" ]; selfContainedBuild = false; but not with ... [ "-p:PublishAot=true" ]; selfContainedBuild = false; which is what my friend seems to want me to try. | 17:32:47 | |
| If they're mutually exclusive on the Dotnet side then that's completely fine, I will just have to make sure he's aware of that fact. 😅 | 17:33:36 | |
| Or this is a huge misunderstanding on my part with the dev, ugh 😓 Oh well, I'll figure it out eventually. Thanks for the thoughts Emma and 6pak! | 17:41:12 | |
| Okay, sorry, I think I've figured out the situation again and I was slightly wrong.
| 17:55:28 | |
| * Okay, sorry, I think I've figured out the situation again and I was slightly wrong.
| 17:56:00 | |
Download image.png | 17:56:11 | |
buildDotnetModule is adding the PublishTrimmed=false | 17:56:20 | |
I assume publishaot simply overrides --no-self-contained when using dotnet cli normally | 17:56:40 | |
| That's my assumption too, yeah. | 18:02:55 | |
| Is there a good way to print the used flags used during a build? I feel like that might help expose what's being done "incorrectly"... | 18:07:28 | |
In the mean time, I'm testing "-p:PublishTrimmed=true" as a dotnetInstallFlags option to see what happens. | 18:09:57 | |