| 14 Aug 2023 |
 mdarocha | fetch-deps runs nuget-to-nix internally | 07:45:59 |
| mdarocha | what problem did you run into that you had to run nuget-to-nix? | 07:46:17 |
 Emma [it/its] | my issue is that its missing a framework dependency | 07:46:22 |
| Emma [it/its] | i dont remember, its been ages and i stuck with it | 07:46:39 |
| mdarocha | are you trying to package a .net framework app? | 07:46:56 |
| Emma [it/its] | no, im building a blazor wasm app | 07:47:11 |
| mdarocha | oh yeah, the error you posted above right | 07:47:45 |
| mdarocha | hmm seems like this package is restored differently internally | 07:47:58 |
| Emma [it/its] | i had to explicitly add this line to deps.nix for my project to fix that error:
(fetchNuGet { pname = "Microsoft.NETCore.App.Runtime.Mono.browser-wasm"; version = "7.0.9"; sha256 = "PHY9n/4/MY3FdnsQWXr/UyByzSxStzcXt11Ys9reN8w="; }) | 07:48:01 |
| mdarocha | and it’s not being picked up by nuget-to-nix | 07:48:14 |
| mdarocha | yeah that should fix it for now | 07:48:23 |
| Emma [it/its] | now im dealing with a NETSDK1084 (no app host available for specific RuntimeIdentifier) | 07:48:32 |
| Emma [it/its] | In reply to @magikarpz:matrix.org
and it’s not being picked up by nuget-to-nix because its a framework dep, not a project dep | 07:48:47 |
| mdarocha | it’ll need to be fixed upstream in nixpkgs | 07:48:55 |
| Emma [it/its] | i guess so, since it has a package type of DotnetPlatform | 07:49:23 |
| mdarocha | that can also be because of a missing nuget | 07:49:42 |
| mdarocha | most of the platform packages are bundled with the dotnet-sdk package in nixpkgs | 07:50:03 |
| Emma [it/its] | yeah this one is just missing | 07:50:14 |
| mdarocha | but i guess all the blazor stuff isn’t there, so it has to be added | 07:50:19 |
 Yarek T | Hmm, with dotnet you usually specify all the dependencies in its <foo>.csproj file, and they get pulled down in a restore step. Does Nix replace that somehow? | 16:39:14 |
| Yarek T | I suppose it wants to if it needs reproducible builds | 16:39:25 |
| Yarek T | Oh, are you using dotnetCorePackages.sdk_7_0 or pkgs.dotnet-sdk_7 ? because the former doesn't package aspnetcore even though it says it should | 16:41:49 |
| Yarek T | Oh wait, isn't mono like completely gone from dotnet these days? Hmm. Is this thing open source? Do you have something I can replicate on my machine? | 16:46:26 |
| mdarocha | dotnet-sdk_7 is an alias to dotnetcorePackages.sdk_7_0, so I don't know how you can encounter differences between the two | 16:51:04 |
| mdarocha | they both point to a packaged sdk, which should contain the aspnetcore framework files | 16:51:23 |
| mdarocha | In reply to @yarekt:matrix.org
Hmm, with dotnet you usually specify all the dependencies in its <foo>.csproj file, and they get pulled down in a restore step. Does Nix replace that somehow? in case of Nix, it runs dotnet restore and then builds a deps.nix based on the restored nugets. This doesnt always work, cause sometimes (ie. in case of alternative sdk packages) not all nugets are pulled at restore | 16:52:24 |
| mdarocha | but most framework and SDK stuff is included by default when using buildDotnetModule, so it isn't usually a problem | 16:52:53 |
| mdarocha | the error like with blazor is mostly probably due to missing stuff in the dependencies included by default, which aren't also properly picked up into deps.nix | 16:53:40 |
| mdarocha | unless there's some other problems, it would also help with debugging to share a repo with a reproduction of the problems | 16:54:19 |
| mdarocha | * unless there's some other problems, it would also help with debugging to share a repo with a reproduction of the errors | 16:54:24 |
