Migrate MobiFlight to .NET 5 or newer

[neilenns]

Discussion related to #484

[MobiFlight-Admin]

Yeah!

[neilenns]

I'm just an innocent bystander on this one 😂 With the firmware PlatformIO migration, input shift registers, and my hacking on STM32 I'm just observing this one till it's done and I can do the build automation.

[gyssels]

@MobiFlight-Admin Just ignore the creation of the branch, I created a folder for .net5 so when I'll PR, I will be invisible to others users... we can reside together.

I am busy with CommandManager now, there is a nasty dependency with the forms on mobiflightconnector

by the way, you guys are crazy to accept PR on main! you should have a "develop" branch...

[neilenns]

If we're gonna debate branching strategies it better be over beer and snacks somewhere!

[gyssels]

FEEDBACK CommandMessenger I just have a deep look for CommandMessenger. the compilation doesn't go well

The project will only compile targeting the ".Net5.0-windows", that is a subset of the
“.Net5.0”. Libraries like System.IO.Ports targets “.Net5.0”.
".Net5.0-windows" can call “.Net5.0”, and “.Net5.0” can’t call ".Net5.0-windows".
This issue make,s for example, the need to modify the tests projects as windows forms application to be able to run the tests, but I cannot guarantee its works, as I have exceptions in VisualStudio test runner that specs “.Net5.0” and not “.Net5.0-windows”

It can be an issue if MobiFlight cannot have a standard test suite…

Besides, the modification to CommandMessenger will include a substitution of the calls to libraries that are deprecated/obsolete in .Net5 and throws an exception:

BinaryFormatter.Serialize (Microsoft docs states to change code to use JsonSerializer ou XmlSerializer, an extension of modifications rest to be determined)
BinaryFormatter.Deserialize
Thread.Abort() (not an equivalent, the thread approach should be revisited)

Conclusion:
As you probably know CmdMensager is a dead library (as that has its last updates in 2017, with a bunch of PR are abandoned between 2017-2021).
If (it's viable to migrate) {
1) Major overhaul of a “dead” library
2) Full depart from the CmdMenssager
3) Probably needs its own GitHub depot
}
Else If (it's NOT viable to migrate){
1) hunt for another maintained library (maybe one of your Arduinos guys can pinpoint one…)
}

[gyssels]

FEEDBACK FSUIPCClient NuGet for FSUIPC Client .Net5 available