| 14 Dec 2025 |
 Corngood | 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 |
| Corngood | 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 |
 Emma [it/its] | dotnet uses those for the "more out there" targets (ios, android, webassembly, afaik) | 03:12:09 |
| Emma [it/its] | in my case, standalone webassembly ^^' | 03:13:36 |
| Emma [it/its] | checked the project's csproj, that's a blazor server app | 03:23:26 |
| Emma [it/its] | <Project Sdk="Microsoft.NET.Sdk.Web"> vs <Project Sdk="Microsoft.NET.Sdk.BlazorWebAssembly"> :) | 03:23:57 |
| Emma [it/its] | 
Download clipboard.png | 03:30:21 |
| Emma [it/its] | i guess it might be worthwhile to test with the new dotnet version lol | 03:30:30 |
| Corngood | 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 |
| Emma [it/its] | a regular dotnet build works fine, which is the weird part | 03:33:55 |
| Emma [it/its] | or rather, it works under a regular shell, hence im surprised it doesnt under buildDotnetModule? | 03:36:49 |
| Corngood | Maybe it has to do with the `--runtime` flag? | 03:50:51 |
| Emma [it/its] | maybe? | 03:58:47 |
| Emma [it/its] | ah yeah, i guess it defaults to --runtime browser-wasm for blazor wasm projects | 04:00:27 |
| Emma [it/its] | any suggestiosn of stuff i could try? | 04:01:08 |
| Corngood | 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 |
| Emma [it/its] | TIL that exists | 04:36:22 |
| Emma [it/its] | yeah, that worked, interesting | 04:40:41 |
| Emma [it/its] | huh interesting | 04:45:02 |
| Emma [it/its] | it restored correctly, but then doesnt build | 04:45:10 |
| Emma [it/its] | /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 |
| Corngood | Does that happen with the flag when you build it outside the sandbox? | 04:50:37 |
| Emma [it/its] | that fails in a completely different way:
/nix/store/jl3858nslcfn094yhs51hgq7sg6ksv6r-dotnet-sdk-10.0.100/share/dotnet/sdk/10.0.100/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.ImportWorkloads.targets(38,5): error NETSDK1147:
To build this project, the following workloads must be installed: wasm-tools
To install these workloads, run the following command: dotnet workload restore
| 04:51:10 |
| Emma [it/its] | doesnt take much to reproduce either: dotnet new blazor-wasm | 04:51:55 |
| Corngood | That error might be from restore unless you're using --no-restore? | 04:52:20 |
| Corngood | In reply to @emma:rory.gay
doesnt take much to reproduce either: dotnet new blazor-wasm We 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 |
| Emma [it/its] | you shouldnt even need the workload | 06:16:39 |
| Emma [it/its] | i dont have the workload, and never had it (and no im not using anything special here) | 06:16:52 |
| Emma [it/its] | dotnet publish -c Release -r browser-wasm | 06:17:01 |
| Emma [it/its] | as soon as i remove browser-wasm it builds fine | 06:17:13 |
