.NET Core 3.1 is unsupported as of December 2022

[SmirbYrneh420]

.NET 3.1 Core is unsupported. Every MFE user is being at risk because of this.

We really need to upgrade .NET version to either 6.0 or 7.0.

[dongle-the-gadget]

It would involve lots of major changes to the UI, that's for sure. We currently do have something else cooking though. If you are asking what, it's a secret. (or open secret I would say)

[dongle-the-gadget]

I do need to wait for @xmine64 to have some time to work on this project though.

[xmine64]

We already know and we are considering a solution. That's just I don't have enough time to work on it but @dongle-the-gadget made some good progresses on it and I consider that as v2.0 of MFE. Still v1.3 will be released with .NET Core 3.1, It has been ready since 2 months ago but we are waiting for translators for releasing it (I guess I should just remove out of date translations and release it right away, waiting is enough). We are considering several options for the future of MFE:

• Using WinUI 3: That way we have to use legacy context menu for tray icon
• Using .NET Framework 4.8: I need to investigate if it works with WinUI 2 or not, last time it wasn't working Doesn't work
• Keep using .NET Core 3.1 until our C++ port is done: It's the secret project that @dongle-the-gadget has been working on it and he's waiting for me to done porting XclParser to C++.

There's also one more option: We can separate MFE core and MFE UI into 2 different apps. Then we can have a "headless" MFE (as requested by an user in #56) and we can implement it with whatever runtime we want, and just port UI related stuff to C++ and use an IPC mechanism to send messages from UI to core.

We will need help from people who know more, to choose the best solution and implement it.

[greenhat616]

@xmine64 There's also one more option: We can separate MFE core and MFE UI into 2 different apps. Then we can have a "headless" MFE (as requested by an user in #56 (comment)) and we can implement it with whatever runtime we want, and just port UI related stuff to C++ and use an IPC mechanism to send messages from UI to core.

It sounds great. This workflow like electron App, which is embedded binary libraries: 1Password 8, Visual Studio Code, etc.
If the team is more familiar with C# than C++, I think it would be good to choose this workflow.

In addition, Microsoft seems to be considering making C#'s UI library more diverse at present, and CPP seems to have not been updated for a long time. MAUI, WINUI 3, etc.

[bigplayer-ai]

Can someone build MicaForEveryone in .NET 6 and upload for us the installation link?

[dongle-the-gadget]

Doing that would be extremely hard without a UI rewrite.

[xmine64]

@bigplayer-ai It can't be achieved easily with just rebuilding as Xaml Island support is removed in newer versions of .NET.

[dongle-the-gadget]

Not really, atm.

[Flaflo]

This is very serious business, please note this in your readme!

[Dhyfer1]

Seriously, MFE needs to be updated so it can work with the latest version of .NET

[alex89912]

any update? everyone is at risk at every time

[UnderCooled]

Here is an C++ implementation.

[dongle-the-gadget]

Note though unofficial