Migration to .NET 5.0 about modernflyouts HOT 12 CLOSED

We are not moving to UWP, we are already using some UWP (i.e. WinRT) APIs such as GlobalSystemMediaTransportControlsSession.

We are going to make the app packaged/app-container compatible (not only the store version but also the Github version), so that both versions will behave same (we can remove the current startup method and app configs which will eliminate those two recent bugs). We will have some advantages like toast notifications, start menu jump lists (we can replace the tray icon with this), startup task, app configs which the unpackaged apps won't.

I was waiting for .NET 5 to have public availability and it seems now is the time 😀. I don't know how we can enable framework packages so that store will install .NET 5 runtime for us and update it automatically. Will dig into that.

from modernflyouts.

Performing well, only issue is a reoccurrence of the can only build for x86 bug

from modernflyouts.

Could we switch to .NET 5 immediately.

yes if we fix the x86 only bug

We could do a 0.6.5 release with the update being switching to .net5

from modernflyouts.

yes i think so we can have a minor 0.6.5 release switching to .net 5

from modernflyouts.

I don't know if .NET 5 is supported by MSIX.

But if so, .NET 5 has an incredible way to trim dependency size

We can keep using .NET Framework 4.6.2 for MSIX if it supports it or move to .NET Core 3.1 immediately

from modernflyouts.

.NET 5 is support has been added to MSIX on beta Visual Studio

from modernflyouts.

Wow! that's awesome. We now just have to wait for our dependencies to target .NET 5

from modernflyouts.

just created a very rough test .net5 build that seems to work in my fork in the .net5 testing branch

from modernflyouts.

Perfect! What about the publish issues?

from modernflyouts.

Could we switch to .NET 5 immediately. Because we may have to be concrete on what runtime we choose before I start working on v0.7

Are there any issues with the .NET 5 build and packaging?

from modernflyouts.

So the first thing to do before starting v0.7 work will be to switch to .NET 5, right?

from modernflyouts.

Just released 0.6.5.
Still a few more things to do to finalise .NET5 integration:

• convert to .dll to fix x86 issue
• fix issue that is preventing implementation of PublishTrimmed

from modernflyouts.