Announcing .NET 6 Preview 1
От: Serginio1 СССР https://habrahabr.ru/users/serginio1/topics/
Дата: 18.02.21 07:15
Оценка: +1
Announcing .NET 6 Preview 1
и солнце б утром не вставало, когда бы не было меня
Re: Announcing .NET 6 Preview 1
От: VladCore  
Дата: 18.02.21 10:25
Оценка:
Здравствуйте, Serginio1, Вы писали:

S>Announcing .NET 6 Preview 1


А где tfm6.0-linux?

https://devblogs.microsoft.com/dotnet/announcing-net-6-preview-1/#targeting-net-6
Re[2]: Announcing .NET 6 Preview 1
От: Serginio1 СССР https://habrahabr.ru/users/serginio1/topics/
Дата: 18.02.21 10:42
Оценка:
Здравствуйте, VladCore, Вы писали:

VC>Здравствуйте, Serginio1, Вы писали:


S>>Announcing .NET 6 Preview 1


VC>А где tfm6.0-linux?


VC>https://devblogs.microsoft.com/dotnet/announcing-net-6-preview-1/#targeting-net-6


https://github.com/dotnet/designs/blob/main/accepted/2020/net5/net5.md#why-is-there-no-tfm-for-linux

Why is there no TFM for Linux?
The primary reason for OS specific TFMs is to vary API surface, not for varying behavior. RIDs allow varying behavior and have support for various Linux flavors. Specifically, TFMs aren't (primarily) meant to allow calling P/Invokes under #if, most of the time that should be done by doing runtime checks or by using RIDs. The primary reason for a TFM is to exclude large amounts of managed representations for OS technologies (WinForms, WPF, Apple's NS APIs, Android etc).

Also, Android, iOS, macOS, and Windows share that they offer a stable ABI so that exchanging binaries makes sense. Linux is too generic of a concept for that, it's basically just the kernel, which again boils down to the only thing you can do is calling P/Invokes.

и солнце б утром не вставало, когда бы не было меня
 
Подождите ...
Wait...
Пока на собственное сообщение не было ответов, его можно удалить.