Sharex: .NET Core / .NET 5 future

[RheaAyase]

Hello,

as we all should know by now .NET Framework is dropped and the future is with netcore. I've done a quick search through the issues and haven't found one so here goes...

.NET Core is an open source replacement of .NET Framework and with upcoming 2.0 version _(early summer?)_ should be rather good and it should contain big portion of the necessary stuff. I know that you mentioned "windows native libraries" in other issues related to linux or mac, so I went ahead and generated this portability analysis report[1]. I would like to ask, did you guys check with the problematic libraries what are their plans, whether they consider to replace some of the missing system libraries with something else, etc..?

I'll also link to this article[2] which may be of some help, but then there are so many good resources already out there :)

Cheers!
Radka

 

[Jaex]

https://developers.redhat.com/blog/2016/12/08/observations-porting-from-net-framework-to-net-core/

[Jaex]

498

[RheaAyase]

498 is TWO YEARS OLD

This is about netcore, not about "linux/mac port" and is well on topic, please don't just dismiss it like that.

_And don't you think that I've seen the article when I worked on it with the author? But yes, it does make for a nice use-case of ShareX._

[Jaex]

.NET core topic talked about in #498 on Oct 17, 2016 which is not TWO YEARS OLD.

This is about porting ShareX to Linux (or making ShareX multi platform), hence it is duplicate.

_Don't you think I already checked .NET core stuffs before? I even used it in my one project..._

[RheaAyase]

Porting to Linux is not porting to netcore. Framework is gonna die, this has to happen sooner or later for windows as well, be it 5 years from now, it still will happen one day, and i thought that it would be a good idea to have a tracking issue open, the same approach we take at work with long-term problems. I'm sorry I took your time.

[RheaAyase]

_gg Jaex changed the title from Mac Port to Mac/Linux Port 21 minutes ago_

[Jaex]

What is gg about it? That issue had 21 mentions of "Linux" and people who just check title when searching issues in GitHub could think it is not about Linux too. So I changed title to reflect that...

[RheaAyase]

And I was not searching for linux port, because that's not what this is about. I searched for "core" and it came up with nothing related, that issue was not in the list. That's all.

netcore != linux != mac

[Jaex]

I didn't told you were searching for linux port.

Currently only reason someone will port their desktop app to netcore is for multi platform support. So yeah it is all about linux port in your use case.

Also you keep saying .NET Framework is dropped & Framework is gonna die but you never giving any proofs about it to prove your statement. In current state even porting console apps to netcore is too difficult. When I'm porting my console app to netcore I needed to remove countless basic stuffs which not exists in netcore to make it compileable. So even if netcore gonna catch .NET framework one day, it gonna take so long time. And like I told before it is not certain it will catch up.

[RheaAyase]

netcore 1.1 added over 1300 apis, you probably used 1.0 - and 2.0 is going to improve a lot more again, hence why i'm talking about 2.0 there. Of course it's hard, and as i said, maybe in 5 years we would be able to get there - not now. Doesn't hurt to start looking around. Either way your choice, good bye.

[QuAzI]

Possible workaround: change most of parts to .NET Standard 2.0, change other parts to .NET Core, use Avalonia UI ( https://github.com/AvaloniaUI/Avalonia ) for cross-platform UI development

[jamesqo]

In addition to Avalonia there's also the Eto.Forms framework: https://github.com/picoe/Eto

[ca-rso-n]

Casually looking at this in 2020

[RheaAyase]

Casually reading the dumb discussion about how netcore == linux. So now in 2020 and with .NET 5 on the horizon, do you still think it's equal? It's not, .NET5 will incorporate all of .NET Framework (like I promised Framework is going to die.) While many of these APIs will not be available on Linux.

Also you keep saying .NET Framework is dropped & Framework is gonna die but you never giving any proofs about it to prove your statement. In current state even porting console apps to netcore is too difficult. When I'm porting my console app to netcore I needed to remove countless basic stuffs which not exists in netcore to make it compileable. So even if netcore gonna catch .NET framework one day, it gonna take so long time. And like I told before it is not certain it will catch up.

_Told you so @Jaex._

Perhaps now the presence of this as a long term tracking ticket makes sense?