DotNET - Revision history

Railwhale: group into sections, add intro text from wikipedia

2026-03-25T22:58:45Z

group into sections, add intro text from wikipedia

Lord-Valen: Use the correct command name.

2025-04-26T20:40:20Z

Use the correct command name.

← Older revision		Revision as of 20:40, 26 April 2025
Line 24:		Line 24:
	</syntaxhighlight>		</syntaxhighlight>

	If the <code>fetch-deps</code> script isn't working for whatever reason, you can manually run <code>nuget-to-~~nix~~</code>:		If the <code>fetch-deps</code> script isn't working for whatever reason, you can manually run <code>nuget-to-json</code>:
	<syntaxhighlight lang="shell-session">		<syntaxhighlight lang="shell-session">
	$ dotnet restore --packages=packageDir ./SomeProject.csproj		$ dotnet restore --packages=packageDir ./SomeProject.csproj

Lord-Valen: Only show what is necessary to build with buildDotnetModule in the example. Also update the manual deps example to use nuget-to-json.

2025-04-26T20:39:55Z

Only show what is necessary to build with buildDotnetModule in the example. Also update the manual deps example to use nuget-to-json.

← Older revision		Revision as of 20:39, 26 April 2025
Line 4:		Line 4:
	Example build file:		Example build file:

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix" line="1" start="1">
	{ ~~fetchFromGitHub~~		{
	, dotnetCorePackages		buildDotnetModule,
	, ~~buildDotnetModule~~		dotnetCorePackages,
	}:		}:

	buildDotnetModule ~~rec~~ {		buildDotnetModule {
	pname = "~~some_program~~";		pname = "hello";
	version = "~~some_version~~";		version = "0.1";

	src = ~~fetchFromGitHub {~~		src = ./.;
	~~owner = "some_owner";~~
	~~repo = pname;~~
	~~rev = "v${version}";~~
	~~hash = ""; # use e~~.g. ~~`nix-prefetch-git`~~
	};

	projectFile = "~~SomeProject~~/~~SomeProject~~.csproj";		projectFile = "Hello/Hello.csproj";
	dotnet-sdk = dotnetCorePackages.sdk_8_0;		dotnet-sdk = dotnetCorePackages.sdk_8_0;
	dotnet-runtime = dotnetCorePackages.runtime_8_0;		dotnet-runtime = dotnetCorePackages.runtime_8_0;
	nugetDeps = ./deps.~~nix; # create a blank file here, then populate it with `nix-build -A fetch-deps && ./result`~~		nugetDeps = ./deps.json;

	~~meta = with lib; {~~
	~~homepage = "some_homepage";~~
	~~description = "some_description";~~
	~~license = licenses.mit;~~
	};
	}		}

Line 36:		Line 25:

	If the <code>fetch-deps</code> script isn't working for whatever reason, you can manually run <code>nuget-to-nix</code>:		If the <code>fetch-deps</code> script isn't working for whatever reason, you can manually run <code>nuget-to-nix</code>:
	<syntaxhighlight lang="sh">		<syntaxhighlight lang="shell-session">
	dotnet restore --packages=packageDir ./SomeProject.csproj		$ dotnet restore --packages=packageDir ./SomeProject.csproj
	nuget-to-~~nix~~ packageDir >deps.~~nix~~		$ nuget-to-json packageDir > deps.json
	rm -r packageDir		$ rm -r packageDir
	</syntaxhighlight>		</syntaxhighlight>

Klinger: Category: Development removed (languages not in development category - yet)

2025-03-25T21:10:15Z

Category: Development removed (languages not in development category - yet)

← Older revision		Revision as of 21:10, 25 March 2025
Line 255:		Line 255:
	* https://learn.microsoft.com/en-us/dotnet/core/introduction		* https://learn.microsoft.com/en-us/dotnet/core/introduction

	~~[[Category: Development]]~~
	[[Category:Languages]]		[[Category:Languages]]

Abowen at 10:26, 13 March 2025

2025-03-13T10:26:51Z

← Older revision		Revision as of 10:26, 13 March 2025
Line 213:		Line 213:

	== Example: Running Rider with dotnet & PowerShell ==		== Example: Running Rider with dotnet & PowerShell ==
			Rider has better compatibility when run in FHS mode

	Rider package		Rider package<syntaxhighlight lang="nix">

	<~~syntaxHighlight~~ lang=nix>
	pkgs.jetbrains.rider		pkgs.jetbrains.rider
	</~~syntaxHighlight~~>		</syntaxhighlight>rider-fhs.nix<syntaxhighlight lang="nix">
			{ pkgs ? import <nixpkgs> {} }:
	~~dotnet~~.nix

	<~~syntaxHighlight~~ lang=nix>
	~~with~~ import <nixpkgs> {};

	~~mkShell~~ {		(pkgs.buildFHSEnv {
	name = "~~dotnet~~-env";		name = "rider-env";
	~~packages~~ = [		targetPkgs = pkgs: (with pkgs; [
	(with ~~dotnetCorePackages~~; ~~combinePackages~~ [		dotnetCorePackages.dotnet_8.sdk
	~~sdk_6_0~~		dotnetCorePackages.dotnet_8.aspnetcore
	~~sdk_7_0~~
	~~sdk_8_0~~
	])
	powershell		powershell
	];		]);
	}		multiPkgs = pkgs: (with pkgs; [
	</~~syntaxHighlight~~>		]);
			runScript = "nohup rider &";
	~~To execute Rider~~		}).env
			</syntaxhighlight><syntaxhighlight lang="nix">
	<~~syntaxHighlight~~ lang=~~bash~~>		nix-shell ./rider-fhs.nix
	nix-shell ./~~dotnet~~.nix ~~--run 'nohup rider &'~~		</syntaxhighlight>This can be added as an alias to your shell if you update the reference to an absolute address, such as location within your home directory. <syntaxhighlight>
	</~~syntaxHighlight~~>		run-rider = "nix-shell ~/nix/rider-fhs.nix";
			</syntaxhighlight>
	This can be added as an alias to your shell if you update the reference to an absolute address, such as location within your home directory. ~~e.g. `~~~/nix/~~dotnet~~.nix`

	== Example: multi-SDK installation with local workload installation enabled ==		== Example: multi-SDK installation with local workload installation enabled ==

Fuse: The solution for ".NET: Location not found" seemed to not work anymore after it was updated to be wrapped.

2024-12-23T14:09:17Z

The solution for ".NET: Location not found" seemed to not work anymore after it was updated to be wrapped.

← Older revision		Revision as of 14:09, 23 December 2024
Line 120:		Line 120:

	If running a .NET-build executable you get the above error, make sure the DOTNET_ROOT environment variable is set:		If running a .NET-build executable you get the above error, make sure the DOTNET_ROOT environment variable is set:
	<~~syntaxHighlight~~ lang=nix>		<syntaxhighlight lang="nix">
	environment.sessionVariables = {		environment.sessionVariables = {
	DOTNET_ROOT = "${pkgs.dotnet-sdk}";		DOTNET_ROOT = "${pkgs.dotnet-sdk}/share/dotnet/";
	};		};
	</~~syntaxHighlight~~>		</syntaxhighlight>

	See : https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-environment-variables#net-sdk-and-cli-environment-variables		See : https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-environment-variables#net-sdk-and-cli-environment-variables

Lostmsu: /* Unable to find package */

2024-09-27T04:55:16Z

Unable to find package

← Older revision		Revision as of 04:55, 27 September 2024
Line 157:		Line 157:

	The new parameter <code>--use-current-runtime</code> requires .NET SDK 8+. I believe what it does is explicitly adding packages missing in this runtime vs .NET Standard to packageDir.		The new parameter <code>--use-current-runtime</code> requires .NET SDK 8+. I believe what it does is explicitly adding packages missing in this runtime vs .NET Standard to packageDir.

			If this still does not work, it might indicate a good time to update target frameworks and dependencies.

	== NativeAOT ==		== NativeAOT ==

Lostmsu: added work around for another error: Unable to find package

2024-09-27T04:30:47Z

added work around for another error: Unable to find package

← Older revision		Revision as of 04:30, 27 September 2024
Line 137:		Line 137:

	Wontfix: The project will build only on Windows.		Wontfix: The project will build only on Windows.

			== Unable to find package ==

			<blockquote>

			error NU1101: Unable to find package runtime.any.System.Collections. No packages exist with this id in source(s): nugetSource

			</blockquote>

			Unsure what specific situations cause this, probably has something to do with .NET Standard libraries.

			The workaround is modifying the bits that generate nuget-deps.nix:

			<syntaxhighlight lang="sh">
			dotnet restore --packages=packageDir --use-current-runtime ./SomeProject.csproj
			nuget-to-nix packageDir >deps.nix
			rm -r packageDir
			</syntaxhighlight>

			The new parameter <code>--use-current-runtime</code> requires .NET SDK 8+. I believe what it does is explicitly adding packages missing in this runtime vs .NET Standard to packageDir.

	== NativeAOT ==		== NativeAOT ==

YoshiRulz: For initial nugetDeps file gen, suggest the more convenient method of a blank file

2024-06-25T20:16:47Z

For initial nugetDeps file gen, suggest the more convenient method of a blank file

← Older revision		Revision as of 20:16, 25 June 2024
Line 24:		Line 24:
	dotnet-sdk = dotnetCorePackages.sdk_8_0;		dotnet-sdk = dotnetCorePackages.sdk_8_0;
	dotnet-runtime = dotnetCorePackages.runtime_8_0;		dotnet-runtime = dotnetCorePackages.runtime_8_0;
	nugetDeps = ./deps.nix; # ~~to generate, set to `""`~~, then `nix-build -A fetch-deps && ./result`		nugetDeps = ./deps.nix; # create a blank file here, then populate it with `nix-build -A fetch-deps && ./result`

	meta = with lib; {		meta = with lib; {

Klinger: Category:Languages

2024-06-25T18:33:57Z

Category:Languages

← Older revision		Revision as of 18:33, 25 June 2024
Line 243:		Line 243:

	[[Category: Development]]		[[Category: Development]]
			[[Category:Languages]]