6 Jul 2025 |
| JamieMagee joined the room. | 02:25:27 |
13 Oct 2022 |
| Winter (she/her) joined the room. | 17:56:01 |
12 Nov 2022 |
| 321, jiayou! joined the room. | 09:31:11 |
| 321, jiayou! left the room. | 09:31:52 |
16 Nov 2022 |
| omlet joined the room. | 20:33:57 |
25 Nov 2022 |
| raphi changed their profile picture. | 19:41:53 |
1 Dec 2022 |
| hexa changed their display name from hexa to hexa (22.11 now). | 13:08:55 |
| hexa changed their display name from hexa (22.11 now) to hexa. | 14:38:43 |
12 Jan 2023 |
| daniel joined the room. | 12:58:04 |
daniel | Anyone who has some experience with packaging a .NET-project using flakes? All prior art I’ve found seems to use the legacy way. | 13:02:55 |
Winter (she/her) | In reply to @daniel:nopemail.org Anyone who has some experience with packaging a .NET-project using flakes? All prior art I’ve found seems to use the legacy way. flakes are the same way as the "legacy way," all flakes help with is exposing the package.
what trouble are you running into? | 14:23:13 |
daniel | In reply to @winterqt:nixos.dev
flakes are the same way as the "legacy way," all flakes help with is exposing the package.
what trouble are you running into? How to "expose"/run fetch-deps | 14:24:38 |
Winter (she/her) | just do nix build .#whateverPackage.fetch-deps | 14:25:11 |
daniel | I did that over and over, realized now that I of course called it with the wrong package name. Thanks though! | 14:29:12 |
Winter (she/her) | In reply to @daniel:nopemail.org I did that over and over, realized now that I of course called it with the wrong package name. Thanks though! (was it not erroring?) | 14:31:10 |
daniel | In reply to @winterqt:nixos.dev (was it not erroring?) It was, but I thought that meant that somehow fetch-deps didn't pass through correctly. | 14:33:24 |
17 Jan 2023 |
daniel | Fetch-deps doesn't seem to handle project references correctly, am I observing this right? The script wants to look for the project dependencies in the "nuget.org" source. | 11:07:33 |
raphi | in my experience <ProjectReference> just works, as long both the referring project and the referenced project are part of src example: https://github.com/raphaelr/nugettest if they are separated search for projectReferences in the nixpkgs manual | 11:48:50 |
22 Jan 2023 |
| omlet left the room. | 20:26:21 |
24 Mar 2023 |
| quapka joined the room. | 15:07:46 |
quapka | Hi guys, is there a minimal flake.nix template for a .NET project? | 15:27:17 |
quapka | Non-flake attempt: I am trying to make it work like this:
{ pkgs ? import <nixpkgs> {} }:
pkgs.mkShell {
buildInputs = with pkgs; [ dotnet-sdk_7 dotnet-runtime_7 ];
DOTNET_ROOT = with pkgs; lib.makeBinPath [ dotnet-runtime_7 ];
}
But still failing.
| 15:38:42 |
quapka | Getting You must install .NET to run this application. error message. | 15:38:56 |
quapka | This seems to be enough to get the project up and running:
{ pkgs ? import <nixpkgs> {} }:
pkgs.mkShell {
buildInputs = with pkgs.dotnetCorePackages; [ sdk_7_0 ];
DOTNET_ROOT = with pkgs; "${dotnet-sdk_7}";
}
| 16:38:21 |
quapka | If anyone finds this helpful, this is how I've turned that into a flake.nix :
{
description = "Basic .NET 7 flake";
outputs = { self, nixpkgs, flake-utils }:
flake-utils.lib.eachDefaultSystem
(system:
let pkgs = nixpkgs.legacyPackages.${system}; in
{
devShells.default =
pkgs.mkShell {
buildInputs = with pkgs.dotnetCorePackages; [ sdk_7_0 ];
DOTNET_ROOT = with pkgs; "${dotnet-sdk_7}";
};
}
);
}
| 16:45:51 |
quapka | Hm, any ideas when *.nuspec file is missing? Therefore the nuget-to-nix file seems to file and consequently I can't run buildDotnetModule , becuase it requires the nugetDeps to be set. | 17:32:22 |
26 Mar 2023 |
| rbutani joined the room. | 00:33:02 |
14 Apr 2023 |
| Flafy (moving to @flafy:flafy.dev) joined the room. | 07:32:29 |
| felschr joined the room. | 18:31:55 |
30 Apr 2023 |
| huantian joined the room. | 05:32:59 |