Neil Enns

@Matze2010 lots of off and on discussion about this work in discord lately. I suggest joining the chat in #development before doing anything, Sebastian has a specific chip he wants...

I was thinking it should wait until after the 2.0 release? To give time for people to test and make sure the firmware actually works

Also I ran into trouble when I was doing this locally because my nano has the same vid and PID as the mega

The real way to solve it is to pop a dialogue and ask the user which of the matching boards should be used. That would only need to happen if...

@DocMoebiuz so should we do this or nah? 😂

This is another example of an Uno using the CH340 chip for USB communication. There's no way to tell it apart from a Mega based on VID/PID.

I gave this a first attempt this morning. I got the project migrated to .NET 5.0 and it would build, but when running it kept complaining that the SimConnect DLL...

For a second attempt I think starting fresh and doing an initial upgrade with https://docs.microsoft.com/en-us/dotnet/core/porting/upgrade-assistant-overview would be a good way to go. My first attempt used a different upgrade tool...

It also requires thought to remove some of the folders in the project that probably shouldn't be checked in. E.g. all the CmdMessenger examples get built and result in duplicate...

I wonder if it's possible to build a NuGet package for the MSFS SimConnect DLL?