Nix + dotnet | 113 Members | |
| 23 Servers |
| Sender | Message | Time |
|---|---|---|
| 2 Nov 2025 | ||
| thats the only .nix file i have | 19:34:29 | |
| (i dont want to maintain 6 identical copies of the same file when they only differ in at most 2 lines) | 19:35:22 | |
| Oh, you can also pass a path to fetch-deps itself to override it. That might be easiest | 19:35:27 | |
| yep discovered that one already | 19:35:38 | |
| but i guess that's my best bet | 19:35:44 | |
| Yeah otherwise you need to do an impure eval, maybe using flake compat or something. Passing the path is probably easiest. | 19:37:12 | |
| hm, i wonder what the best way would be to use nix to publish nuget packages | 19:53:00 | |
since packNupkg emits multiple nupkg files, im not sure how ot best deal with thta | 19:53:31 | |
also wondering how to best handle versioning, since my current ci setup uses current time for that | 19:58:31 | |
that's my current ci setup, that i'd like to get rid of | 19:59:17 | |
| 20:09:36 | ||
| oh... i didnt realise but the nupkg files are empty... lol | 21:17:21 | |
| 3 Nov 2025 | ||
| Still trying to package my wonky project. I got a new version of the dll dependencies my partner's nuget server, and a wrapper project that depends on it as source code. I'm puzzled how to set projectFile.
| 18:03:55 | |
| * Still trying to package my wonky project. I got a new version of the dll dependencies my partner's nuget server, and a wrapper project that depends on it as source code. I'm puzzled how to set projectFile.
EDITING | 18:04:02 | |
| * Still trying to package my wonky project. I got a new version of the dll dependencies my partner's nuget server, and a wrapper project that depends on it as source code. I'm puzzled how to set projectFile.
| 18:06:10 | |
A basic question. The .nupkg file with the dlls that should do all the heavy lifting: Should I make a proper package out of it with buildDotnetModule, stdenv.mkDerivation or similar, and pass it to my wrapper project as buildInputs? Or is that not necessary because the dlls are on the nupkg server and should be autodetected through deps.json? | 18:09:42 | |
| * Still trying to package my wonky project. I got a new version of the dll dependencies my partner's nuget server, and a wrapper project that depends on it as source code. I'm puzzled how to set projectFile.
EDIT: Nevermind 2. & 3., it seems that | 18:15:30 | |
not necessary, it'll be detected through deps.json | 20:31:40 | |
| 4 Nov 2025 | ||
| hm, trying to follow the manual but it doesnt seem im able to include a project reference? | 02:09:28 | |
getting this in the fetch-deps script | 02:10:21 | |
fwiw i have <PackageReference Include="ArcaneLibs" Version="*" Condition=" '$(ContinuousIntegrationBuild)'=='true' "/> and projectReferences = [ arcanelibs.packages."${pkgs.stdenv.hostPlatform.system}".ArcaneLibs ]; | 02:11:14 | |
| Does ArcaneLibs have a share/nuget/packages/*.nupkg? | 02:44:32 | |
| * Does ArcaneLibs have a share/nuget/packages/*.nupkg? Edit: actually it's a bit more complicated than that. It should be $out/share/nuget/packages/name/version/... If you use buildDotnetModule with packNupkg = true it'll usually do the right thing. | 02:47:45 | |
| thats what it is yes | 02:49:23 | |
| https://github.com/TheArcaneBrony/ArcaneLibs/blob/master/flake.nix#L33 | 02:49:44 | |
im actually using the output of it to publish to nuget directly (give or take a little usage of the zip package) | 02:50:59 | |
| Can you --keep-failed and see what's in the nuget.config? | 03:24:31 | |
I can reproduce it. There's something about the package it doesn't work, because if I add avalonia from nixpkgs with a similar sort of reference it does work. Maybe it doesn't like the way the version is written? | 03:50:48 | |
| hm, no clue, but i know this works fine with the nuget published builds | 04:48:11 | |
| 08:34:28 | ||