Nix + dotnet | 121 Members | |
| 24 Servers |
| Sender | Message | Time |
|---|---|---|
| 21 Apr 2025 | ||
| 23:29:02 | |
| oh yeah, with the whole illegal image spam fiasco in the main NixOS room, image uploading got restricted | 23:29:10 | |
basically find what you want to change in the nixpkgs monorepo, make the changes you want, commit into a new branch, run nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD" and then run the programs to see if they still work | 23:32:15 | |
| but .NET is more annoying than usual because if you change something in the SDKs, they'll cause every .NET program in nixpkgs to also be rebuilt, so you'll spend quite a few hours on the rebuild | 23:32:49 | |
| I recommend reading parts of the nixpkgs manual first, so you learn how things work in nix, since it's quite different from any other distro | 23:33:20 | |
* basically find what you want to change in the nixpkgs monorepo, make the changes you want, commit into a new branch, run nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD" and then run the programs to see if they still work and make a PR back to the main repo | 23:33:50 | |
| Just to be sure, is this the manual you mean? https://nixos.org/manual/nixpkgs/stable/index.html | 23:34:21 | |
| nixos is unique, but that's what makes it the easiest distro to contribute to imo | 23:34:24 | |
| (and then just stare at your open prs not having any commiters reviewing it) | 23:34:40 | |
| yes | 23:34:45 | |
| it's quite long so I just jump around looking at the parts that I don't understand usually | 23:35:03 | |
| maybe not the best way, but it is the fastest way (and efficient enough for me) | 23:35:19 | |
| Alright, thanks! I'll take a read though what seem like the relevant parts of that, yeah that page is really long. I've read through quite a few man pages though, so it can't be as bad as some of those | 23:36:36 | |
taking 4 pages to say like ls -l will print out the files in a list format lol | 23:36:58 | |
this works as a workaround for installing workloads in home | 23:42:52 | |
| ideally build-dotnet.nix in nixpkgs should just add that file | 23:43:09 | |
| yeah, I might make a PR to do that | 23:43:22 | |
| yeah, seems like only the source-built variants have that:
| 23:44:09 | |
| I hope it just changes the install path but still also discovers workloads from system paths | 23:44:31 | |
| for future declarative workloads | 23:44:41 | |
| 22 Apr 2025 | ||
| I've got dotnet up and running well with the suggested config for it, even after changing vscode its still not able to open a solution, gives me an error "command 'csdevkit.openSolution' not found". Have the following configuration for that:
Any idea what might I be missing here? | 02:27:58 | |
| I can see the extension in vscode, and I can see its command in the F1 menu for opening the solution, its just when I try to do that it gives me that error | 02:29:45 | |
| 23 Apr 2025 | ||
| well, I think I've figured out why. On the docs for that extension, they have a section with a list of reasons why the command might not be found:
Which I think would mean it doesn't work on NixOS, right? | 04:37:29 | |
| No, it should work since I patch it to work under those conditions | 05:28:03 | |
| but if you are having troubles with that, you can open an issue and mention me, since I'm the maintainer for them | 05:28:16 | |
| just make sure to get the logs from the Extension Host, C# DevKit and C# extensions | 05:28:32 | |
| I have not been able to get it to work properly yet, even though I am already using pkgs.vscode.fhs. Are there any instructions on what we need to get it to run properly? | 10:23:41 | |
| Would this be enough info? Neither C# or C# DevKit have any logs in the output window, only that one. This package is installed though Extension Host:
| 13:06:12 | |
| yeah, you're missing that extension, it won't work without it | 15:00:06 | |
| even though it's pointless to have it since there's no dynamic installing of .NET, it's needed for them to work | 15:00:37 | |