Nix + dotnet | 120 Members | |
| 24 Servers |
| Sender | Message | Time |
|---|---|---|
| 11 Dec 2025 | ||
| https://github.com/NixOS/nixpkgs/pull/469483 10.0.1 update is here. I already ran nixpkgs-review, tests, etc, but PR review would be appreciated | 19:07:15 | |
| 14 Dec 2025 | ||
| hmm, can i not package blazor apps? | 03:05:20 | |
|
| 03:05:39 | |
| (blazor webassembly, fwiw) | 03:08:06 | |
| Take a look at https://github.com/NixOS/nixpkgs/pull/469483#issuecomment-3649467851 I'm not sure how closely related this it, but I think `ersatztv` is a blazor app. It seems to work okay, but it ended up being tied to a specific runtime version of a nuget package. | 03:09:53 | |
| Yours is complaining about mono though. To be honest I still don't really understand the point of those mono runtime packages | 03:11:29 | |
| dotnet uses those for the "more out there" targets (ios, android, webassembly, afaik) | 03:12:09 | |
| in my case, standalone webassembly ^^' | 03:13:36 | |
| checked the project's csproj, that's a blazor server app | 03:23:26 | |
<Project Sdk="Microsoft.NET.Sdk.Web"> vs <Project Sdk="Microsoft.NET.Sdk.BlazorWebAssembly"> :) | 03:23:57 | |
Download clipboard.png | 03:30:21 | |
| i guess it might be worthwhile to test with the new dotnet version lol | 03:30:30 | |
| Ah okay, that's the only blazor thing I've come across. That mono package hasn't been published on nuget.org since 8, so isn't it weird that it's looking for v10? | 03:32:52 | |
a regular dotnet build works fine, which is the weird part | 03:33:55 | |
or rather, it works under a regular shell, hence im surprised it doesnt under buildDotnetModule? | 03:36:49 | |
| Maybe it has to do with the `--runtime` flag? | 03:50:51 | |
| maybe? | 03:58:47 | |
ah yeah, i guess it defaults to --runtime browser-wasm for blazor wasm projects | 04:00:27 | |
| any suggestiosn of stuff i could try? | 04:01:08 | |
| You should be able to override the runtime id. We should probably add a test project for this, and for the server one as well. | 04:14:35 | |
| TIL that exists | 04:36:22 | |
| yeah, that worked, interesting | 04:40:41 | |
| huh interesting | 04:45:02 | |
| it restored correctly, but then doesnt build | 04:45:10 | |
/nix/store/jl3858nslcfn094yhs51hgq7sg6ksv6r-dotnet-sdk-10.0.100/share/dotnet/sdk/10.0.100/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(190,5): error NETSDK1084: There is no application host available for the specified RuntimeIdentifier 'browser-wasm'. [/build/source/Utilities/Spacebar.AdminApi.TestClient/Spacebar.AdminApi.TestClient.csproj] | 04:45:28 | |
| Does that happen with the flag when you build it outside the sandbox? | 04:50:37 | |
| that fails in a completely different way: | 04:51:10 | |
doesnt take much to reproduce either: dotnet new blazor-wasm | 04:51:55 | |
| That error might be from restore unless you're using --no-restore? | 04:52:20 | |
In reply to @emma:rory.gayWe should probably just make the test based on this template project. I also haven't figured out the whole workload thing or how we can support it | 04:53:26 | |