| 1 Dec 2024 |
 Emma [it/its] | i cant open any projects under neither steam-run or plain | 00:54:20 |
| Emma [it/its] | 2024-12-01 02:09:50,925 [ 3385] SEVERE - #c.i.o.p.i.ProjectManagerImpl - project loading failed
java.lang.IllegalStateException: No protocolHost for the application
at com.jetbrains.rider.protocol.ApplicationProtocolKt.K(ApplicationProtocol.kt:73)
at com.jetbrains.rider.protocol.ApplicationProtocolKt.getProtocolManager(ApplicationProtocol.kt:22)
at com.jetbrains.rider.projectView.SolutionInitializer.initSolution(SolutionInitializer.kt:37)
at com.jetbrains.rider.projectView.SolutionManager.K(SolutionManager.kt:465)
[...]
| 01:10:14 |
| Emma [it/its] | i couldnt find anything on their bug tracker about it | 01:10:24 |
| Emma [it/its] | can reproduce if i pull Rider from 24.11 | 03:04:16 |
| Emma [it/its] | okay, importing rider from 24.05 works fine, in comparison | 04:08:23 |
| Emma [it/its] | so it seems to be an issue with whatever rider version is shipped in 24.11 and unstable | 04:08:52 |
| 2 Dec 2024 |
|  dish [Fox/It/She] changed their profile picture. | 19:59:20 |
 Corngood | https://github.com/NixOS/nixpkgs/pull/360923
Here's a PR that adds dotnet-sdk_9, etc. I intend to backport it to 24.11.
I'm curious what people think about sdk/runtime naming. We currently have minor version SDKs that aren't accessible at the top level, e.g. dotnetCorePackages.sdk_8_0_1xx.
Should we add dotnet-sdk_8_0_1xx?
| 23:02:20 |
| 3 Dec 2024 |
|  lostmsu joined the room. | 01:41:23 |
| lostmsu | Just saying hi as a new member here | 01:42:27 |
| Emma [it/its] | In reply to @corngood:corngood.com
https://github.com/NixOS/nixpkgs/pull/360923
Here's a PR that adds dotnet-sdk_9, etc. I intend to backport it to 24.11.
I'm curious what people think about sdk/runtime naming. We currently have minor version SDKs that aren't accessible at the top level, e.g. dotnetCorePackages.sdk_8_0_1xx.
Should we add dotnet-sdk_8_0_1xx?
i think the current system of having those symlink to latest major releases is fine | 06:50:27 |
 Emmanuel Genga | How do you guys install dev certs on your machine for development of Dotnet web apps | 12:27:46 |
| 4 Dec 2024 |
| Emma [it/its] | i dont, i jut get rid of https alltogether | 13:24:57 |
| Emma [it/its] | dont even need to worry about restricted APIs because browsers treat localhost as always-secure rather than making it conditional on https | 13:25:38 |
| lostmsu | What is the difference between dotnetCorePackages.dotnet_9.sdk and dotnet-sdk_9? | 19:21:55 |
| Corngood | nothing. they're the same package | 19:22:55 |
| lostmsu | Hm, is there a plan to remove one of them to avoid confusion? | 19:23:26 |
| Corngood | I originally had it in mind to remove the top level aliases, but now I'm not so sure. I added dotnet-sdk_9 recently to be consistent with the other versions. | 19:25:05 |
| lostmsu | 
Download image.png | 19:28:09 |
| lostmsu | There's a bit more of confusion: there's no dotnet-aspnetcore_8 | 19:28:20 |
| Corngood | There is, but dotnet-aspnetcore is an alias for it | 19:28:54 |
| Corngood | What's that from? Maybe we can clean up what's being reported a bit | 19:29:26 |
| lostmsu | https://search.nixos.org/packages?channel=24.11&from=0&size=50&sort=relevance&type=packages&query=dotnet-aspnetcore | 19:29:35 |
| lostmsu | This is what I'm currently using as a app/package store for NixOS | 19:29:57 |
| lostmsu | really not the best thing for it, does anyone know anything better? | 19:30:21 |
| Corngood | I'm sorry, this is wrong. dotnetCorePackages.dotnet_9.sdk is the source-built sdk, and dotnet-sdk_9 is the binary SDK. | 19:31:34 |
| Corngood | dotnet-sdk_9 is an alias of dotnetCorePackages.sdk_9_0 | 19:31:49 |
| lostmsu | should one care? | 19:31:59 |
| Corngood | Not really. At some point I'd like to make the top level aliases point at the source-built versions. Once they build reliably on all platforms. | 19:32:59 |
| Corngood | * +nothing. they're the same package+ | 19:33:40 |
