| 21 Apr 2025 |
 GGG | IntelliCode I don't know if anyone has properly packaged yet | 23:10:05 |
| GGG | oh, those | 23:10:14 |
| GGG | yeah, seems nobody has packaged them | 23:10:31 |
 corruptcomputer | Yeah all the rest I have installed are there now, not sure if I just missed them before or if they were newly added | 23:10:38 |
| GGG | you could try installing it directly from the marketplace and see if they work, if not you might have to try to package them yourself | 23:10:49 |
| GGG | or use the fhs vscode version, since that usually has better compatibility with htings | 23:11:00 |
| GGG | * or use the fhs vscode version, since that usually has better compatibility with things | 23:11:02 |
| corruptcomputer | Alright, thanks! I'll try to get that setup with those plugins, I think those 2 being installed manually using the like
{
name = "vscode-entity-framework";
publisher = "richardwillis";
version = "0.0.20";
sha256 = "0karaxnaalhr08n7dyc89wr5i3y9jxa5nfiyqcxdg4ws0p3zcsbk";
}
{
name = "vscode-avalonia";
publisher = "avaloniateam";
version = "0.0.32";
sha256 = "1vrsnq7v0p508c077g62yy2h9l8dqgad5929nnyqiys3bcx5ksnq";
}
syntax shouldn't be too bad, was not super happy with installing like 10 extensions that way tho | 23:13:59 |
| corruptcomputer | Since afaik, they don't update very often | 23:14:08 |
| corruptcomputer | But those others from MS have constant updates to them | 23:14:55 |
| GGG | Well, if you are using flakes you could use the bot-updated VSCode extensions flake | 23:15:17 |
| GGG | If not, you can just install them from the VSCode Marketplace and have VSCode auto update them itself | 23:15:32 |
| GGG | Just gotta take care to not update the C# ones | 23:15:41 |
| corruptcomputer | I don't use flakes yet, still trying to learn base NixOS before trying to dig into some of those more advanced features. I did see that home-manager also had a way to do it, but that also looked quite complex to setup | 23:16:08 |
| GGG | Fair enough | 23:16:25 |
| GGG | I'd recommend you don't really bother with it for now and let VSCode manage the extensions that aren't packaged in nixpkgs for now | 23:16:48 |
| corruptcomputer | yeah I think thats what I'm going to do for now, eventually I'll get around to looking at those other options | 23:17:20 |
| corruptcomputer | Thanks again for your help! | 23:17:27 |
| GGG | no problem! | 23:17:33 |
| GGG | I'm considering making a dotnet module to help people have a good .NET setup and avoid some of those pitfalls I mentioned (fixed env var, using runtime and sdk at the same time, etc.) | 23:18:11 |
| corruptcomputer | that would be fantastic if possible, something like environment.development.dotnet.enable = true; or similar would be so nice to have | 23:19:35 |
| GGG | I was thinking of something like programs.dotnet.enable = true and then you pick the versions you want and it'll configure env vars, files in /etc and stuff to make it work properly | 23:20:08 |
| GGG | then later on when MS finally figures out how they're gonna let distros package workloads it could tap onto that as well | 23:20:23 |
| corruptcomputer | Oh wait a minute, is it not possible to install the aspire workload with this? | 23:21:11 |
| corruptcomputer | I need that for my app to work... | 23:21:17 |
| GGG | since the directory where .NET lives is read-only, dotnet workload install doesn't work | 23:21:30 |
| GGG | I have no idea how to get workloads working with .NET in NixOS since I haven't used them myself | 23:21:44 |
| GGG | oh nevermind | 23:22:10 |
| GGG | apparently userlocal file instructs .NET to do the install per user | 23:22:23 |
| GGG | so it should be fine, my bad | 23:22:28 |
