AUR (en) - dotnet-core-bin

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: dotnet-runtime-bin 10.0.10.sdk302-1

Package Actions

Git Clone URL:	https://aur.archlinux.org/dotnet-core-bin.git (read-only, click to copy)
Package Base:	dotnet-core-bin
Description:	The .NET Core runtime (binary)
Upstream URL:	https://www.microsoft.com/net/core
Keywords:	.net dotnet microsoft
Licenses:	MIT
Conflicts:	dotnet-runtime, dotnet-runtime-10.0
Provides:	dotnet-runtime, dotnet-runtime-10.0
Submitter:	Gr3q
Maintainer:	Gr3q
Last Packager:	Gr3q
Votes:	58
Popularity:	0.24
First Submitted:	2019-10-02 17:13 (UTC)
Last Updated:	2026-07-22 08:15 (UTC)

Dependencies (9)

dotnet-host (dotnet-host-rc-bin^AUR, dotnet-host-preview-bin^AUR, dotnet-host-bin^AUR, dotnet-host-bin^AUR)
glibc (glibc-git^AUR, glibc-git-native-pgo^AUR, glibc-eac^AUR)
icu (icu-git^AUR)
libgcc (libgcc-fast-optimized^AUR, libgcc-snapshot^AUR)
libstdc++ (libstdc++-fast-optimized^AUR, libstdc++-snapshot^AUR)
libunwind (libunwind-carbon^AUR, libunwind-git^AUR)
openssl (openssl-git^AUR, openssl-aegis^AUR, openssl-static^AUR)
zlib (zlib-git^AUR, zlib-ng-compat-git^AUR, zlib-ng-compat)
lttng-ust2.12 (optional) – CoreCLR tracing

Required by (207)

am2rlauncher (requires dotnet-runtime)
am2rlauncher-git (requires dotnet-runtime)
application-inspector-bin (requires dotnet-runtime)
appveyor-server (requires dotnet-runtime)
archisteamfarm-bin (requires dotnet-runtime)
artemisrgb-git (requires dotnet-runtime)
aspnet-runtime-bin
autumn-git (requires dotnet-runtime)
avalonia-ls-git (requires dotnet-runtime)
avalonia86 (requires dotnet-runtime)
avaloniailspy (requires dotnet-runtime)
avaloniailspy-git (requires dotnet-runtime)
avaloniatftpclient-bin (requires dotnet-runtime)
azure-functions-core-tools-bin (requires dotnet-runtime) (optional)
baballonia (requires dotnet-runtime-10.0)
bassboom-2 (requires dotnet-runtime-10.0)
bassboom-2-git (requires dotnet-runtime-10.0)
bassboom-3 (requires dotnet-runtime-10.0)
bassboom-3-git (requires dotnet-runtime-10.0)
beditor-bin (requires dotnet-runtime)
Show 187 more...

Sources (4)

Pinned Comments

Gr3q commented on 2019-10-05 07:28 (UTC) (edited on 2021-02-13 09:06 (UTC) by Gr3q)

IMPORTANT INSTALLATION INFO (a reminder for myself as well):

For dotnet to work you need to EXPLICITLY install:

ONE dotnet-host - highest version possible
ANY NUMBER of dotnet-runtimes (and its sdks after if you want to build as well - Right now version 'bin', '3.1', '3.0', '2.2' and '2.1' are tested to work together)

If you keep the install order in mind and you don't rely on pacman to resolve your dependencies you will be fine.

Longer explanation:

Every dotnet-sdk is dependent on a specific version of dotnet-runtime, this is built into dotnet.

Technically you only need the latest dotnet-sdk because it can build to any earlier versions.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 12 Next › Last »

cryptozio commented on 2024-08-16 11:51 (UTC)

I think those are related that I installed maui-android and android workloads through dotnet workload install command, but how else could I do it.

cryptozio commented on 2024-08-16 11:44 (UTC) (edited on 2024-08-16 11:45 (UTC) by cryptozio)

Any idea why am I getting these? It says those files already exist etc.

błąd: nie udało się dokonać transakcji (konfliktujące pliki) dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/8.0.100/microsoft.net.workload.emscripten.current/8.0.8/WorkloadManifest.json znajduje się w systemie plików dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/8.0.100/microsoft.net.workload.emscripten.current/8.0.8/WorkloadManifest.targets znajduje się w systemie plików dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/8.0.100/microsoft.net.workload.emscripten.net6/8.0.8/WorkloadManifest.json znajduje się w systemie plików dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/8.0.100/microsoft.net.workload.emscripten.net6/8.0.8/WorkloadManifest.targets znajduje się w systemie plików dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/8.0.100/microsoft.net.workload.emscripten.net7/8.0.8/WorkloadManifest.json znajduje się w systemie plików dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/8.0.100/microsoft.net.workload.emscripten.net7/8.0.8/WorkloadManifest.targets znajduje się w systemie plików dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/8.0.100/microsoft.net.workload.mono.toolchain.current/8.0.8/WorkloadManifest.Wasi.targets znajduje się w systemie plików dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/8.0.100/microsoft.net.workload.mono.toolchain.current/8.0.8/WorkloadManifest.json znajduje się w systemie plików dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/8.0.100/microsoft.net.workload.mono.toolchain.current/8.0.8/WorkloadManifest.targets znajduje się w systemie plików dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/8.0.100/microsoft.net.workload.mono.toolchain.current/8.0.8/WorkloadTelemetry.targets znajduje się w systemie plików dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/8.0.100/microsoft.net.workload.mono.toolchain.current/8.0.8/localize/WorkloadManifest.cs.json znajduje się w systemie plików dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/8.0.100/microsoft.net.workload.mono.toolchain.current/8.0.8/localize/WorkloadManifest.de.json znajduje się w systemie plików dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/8.0.100/microsoft.net.workload.mono.toolchain.current/8.0.8/localize/WorkloadManifest.en.json znajduje się w systemie plików dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/8.0.100/microsoft.net.workload.mono.toolchain.current/8.0.8/localize/WorkloadManifest.es.json znajduje się w systemie plików dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/8.0.100/microsoft.net.workload.mono.toolchain.current/8.0.8/localize/WorkloadManifest.fr.json znajduje się w systemie plików dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/8.0.100/microsoft.net.workload.mono.toolchain.current/8.0.8/localize/WorkloadManifest.it.json znajduje się w systemie plików

Gr3q commented on 2024-06-24 20:29 (UTC)

C# Dev Kit should be working in VSCode with the latest version.

Gr3q commented on 2024-03-11 08:05 (UTC)

@natep Then please send me your email address you use on your account here.

natep commented on 2024-03-07 04:20 (UTC)

@Gr3q Sure! I am game to help keep this up to date. Since this specific update is just a security patch and nothing big changed it is pretty straightforward especially given how well written the scripts are. Just let me know and I'll push.

Gr3q commented on 2024-03-06 08:32 (UTC) (edited on 2024-03-06 08:34 (UTC) by Gr3q)

@natep the Only way is if I orphan the package or I add you as a co-maintainer.

If you feel like you are up to maintaining this package and you are OK with adhering to the info in the pinned comment, I can add you. I will need your email address you are using on the AUR. I will hold off on updating to this evening in case you accept (so you can do it yourself).

I can keep maintaining the other (lower versioned) packages, but this is a time-sensitive and used by lots of people.

Unfortunately I barely have enough time nowadays. I'm surprised of how can I have even less time when even before I had basically no free time.

natep commented on 2024-03-05 01:03 (UTC) (edited on 2024-03-05 01:12 (UTC) by natep)

@Gr3q this has been out of date a little while now and is missing a security patch. For myself, I updated the .SRCINFO and PKGBUILD files. Reading the wiki and searching around I do not offhand see a way to propose an update (e.g., a pull request). Is there a way I can give you a patch to review so folks can update without manually editing files?