| Git Clone URL: | https://aur.archlinux.org/dotnet-core-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | dotnet-core-bin |
| Description: | The ASP.NET Core targeting pack (binary) |
| Upstream URL: | https://www.microsoft.com/net/core |
| Keywords: | .net dotnet microsoft |
| Licenses: | MIT |
| Conflicts: | aspnet-targeting-pack, aspnet-targeting-pack-9.0 |
| Provides: | aspnet-targeting-pack, aspnet-targeting-pack-9.0 |
| Submitter: | Gr3q |
| Maintainer: | Gr3q |
| Last Packager: | Gr3q |
| Votes: | 47 |
| Popularity: | 0.39 |
| First Submitted: | 2019-10-02 17:13 (UTC) |
| Last Updated: | 2025-04-17 07:37 (UTC) |
@cryptozio maybe try to update your workloads? "dotnet workload update"
As a quick sanity check, I spun up a new arch virtual environment and installed dotnet, maui-android and android workloads, installed JDK, Android SDK and created a new "maui" template project. "dotnet build" just worked and at no time did I get an conflicts so I'm really not sure.
Edit: accidentally had workload list instead of update
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.
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
C# Dev Kit should be working in VSCode with the latest version.
@natep Then please send me your email address you use on your account here.
@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.
@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.
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:
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.