| 15 Aug 2023 |
 Emma [it/its] | or at least, it did in our project, didnt check in the repro | 19:57:49 |
| 16 Aug 2023 |
 mdarocha | from what I searched, wasm-tools, needed by the blazor wasm compilation, is packages as a dotnet workload | 06:55:48 |
| mdarocha | and unfortunately, workloads aren't supported in Nix for now - see https://github.com/NixOS/nixpkgs/issues/226107 | 06:56:10 |
| mdarocha | so to make wasm compilation fully work you would need to try to hack together some form of workload support, I know that previously something was attempted for maui | 06:56:44 |
| 19 Aug 2023 |
| Emma [it/its] | shouldnt it be a matter of installing the relevant nuget packages? | 11:46:17 |
| mdarocha | from what I understand workloads work a little bit differently and aren’t covered by the current nix mechanisms | 11:47:47 |
| Emma [it/its] | im guessing the dotnet packages also cant be extended to ship with the workloads builtin? | 11:50:54 |
| mdarocha | there were attempts from what i remember, see the issue i linked above | 11:51:33 |
| mdarocha | but properly implementing workloads in nix would require understanding how they are installed by the dotnet cli so that we can provide them using the standard nix functions | 11:52:14 |
| Emma [it/its] | at least going by https://github.com/NixOS/nixpkgs/blob/nixos-23.05/pkgs/development/compilers/dotnet/versions/7.0.nix, there seems to be a packages array, couldnt the missing ones be added there? | 11:52:19 |
| mdarocha | nope, this package array is used to streamline the package updating process | 11:53:07 |
| Emma [it/its] | it looks like theyre all just installed to /usr/share/dotnet/packs | 11:53:16 |
| Emma [it/its] | * it looks like theyre all just installed to /usr/share/dotnet/packs (arch) | 11:53:21 |
| mdarocha | ie those package are implicitly included with every does, and thanks to that we don’t have to regenerate all the deps.nix in the nixpkgs tree | 11:53:43 |
| mdarocha | if you want to take a stab at implementing workloads then PRs are welcome :) I unfortunately didn’t have the time to take a look at that issue | 11:54:13 |
| Emma [it/its] | both eg. Microsoft.AspNetCore.App.Ref and Microsoft.NETCore.App.Runtime.Mono.browser-wasm appear to be in in that same /usr/share/dotnet/packs directory | 11:54:34 |
| mdarocha | * ie those package are implicitly included with every deps, and thanks to that we don’t have to regenerate all the deps.nix in the nixpkgs tree | 11:54:41 |
