Package Details: dotnet-sdk-bin 5.0.5.sdk202-1

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 SDK (binary)
Upstream URL: https://www.microsoft.com/net/core
Licenses: MIT
Conflicts: dotnet-sdk=5.0.5.sdk202, dotnet-sdk-5.0, dotnet-sdk-bin
Provides: dotnet-sdk=5.0.5.sdk202, dotnet-sdk-5.0, dotnet-sdk-bin
Submitter: Gr3q
Maintainer: Gr3q
Last Packager: Gr3q
Votes: 28
Popularity: 3.30
First Submitted: 2019-10-02 17:13
Last Updated: 2021-04-06 17:32

Required by (54)

Sources (3)

Pinned Comments

Gr3q commented on 2019-10-05 07:28

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

1 2 3 4 Next › Last »

SilentStoat commented on 2021-03-21 23:17

I'm kinda new to this so I might be confused, but it looks like PKGBUILD says that aspnet-runtime-bin, dotnet-runtime-bin, and dotnet-sdk-bin are in conflict with themselves.

Gr3q commented on 2021-03-12 08:15

@servime try install dotnet-host-bin, dotnet-runtime-bin and dotnet-sdk-bin all at once if your AUR manager doesn't handle split packages. use just use makepkg -si after you cloned this repo.

@satcom886 .NET is .NET Core, it was simple renamed after 3.1.

satcom886 commented on 2021-03-11 20:20

@Gr3q Yes, let's add dotNET on Windows too, this is not confusing at all. Ok, so from what I understand:

dotNET Framework - Windows-only libraries and tools for running and developing dotNET programs.
dotNET - Pretty much the same thing, but cross-platform, also without a native ability to create GUIs on Linux (at least until MAUI gets released in v6)
dotNET Core - LTS version of the normal dotNET?

servimo commented on 2021-03-11 19:00

When I try to install dotnet-sdk-bin 5.0.4 in Manjaro from AUR I get this: "target not found: dotnet-sdk-bin", should I wait till dotnet-core-bin is in AUR?

Gr3q commented on 2021-03-11 08:23

You might be talking about the .NET Framework, the framework running WinForms applications. The normal .NET is .NET Core for a while now (renamed simply as .NET)

satcom886 commented on 2021-03-11 08:13

Wow, maybe not actually. I remember dotNET being proprietary, while dotNET Core was supposed to be FOSS. Now I'm not really sure. It looks like Microsoft released dotNET as FOSS.

satcom886 commented on 2021-03-11 08:09

@Gr3q One thing to note is that the packages in the repo are dotNET Core, not dotNET. Normal dotNET is currently at version 5, while dotNET Core is at version 3.1.

AFAIK they are two different things, but often it doesn't matter which one you choose.

Gr3q commented on 2021-03-11 07:55

The purpose of depending on netstandrad-targeting-pack-2.1 is that you have an option either user netstandard-targeting-pack or netstandard-targeting-pack-bin with the AUR packages.

I don't support using the AUR packages along with the official packages because I can't guarantee that they are up to date (as you can see they are on version 3.1 instead of 5).

My recommendation is to use one or the other, because it is more likely to break if they are mixed than not.

amos commented on 2021-03-10 12:39

Well, both dotnet-sdk and and dotnet-targeting-pack (from the official repos) require netstandard-targeting-pack (and not netstandrad-targeting-pack-2.1), and this is not provided, which creates a conflict. I didn't mean to remove the provides of netstandrad-targeting-pack-2.1, just to add the provides of netstandrad-targeting-pack.

Regardless, netstandard-targeting-pack-bin can be safely removed from conflicts and provides, as this is already the package name itself (and is not depended on by anybody).

Gr3q commented on 2021-03-10 07:43

The official package name is netstandard-targeting-pack, but it actually provides netstandard-targeting-pack-2.1.

This package provides netstandard-targeting-pack-2.1 and itself, so it's conflicting the package in the official repos as intended