locked
When to convert WPF .Net framework application to .Net Core? RRS feed

  • Question

  • We've been developing a large WPF application (framework v4.5.2) for a number of years. It's been rolled out to a very small number of customers for testing, but it is essentially still under development. With the advent of .Net Core 3 and now 5 around the corner, I was wondering whether we should be thinking about migrating our solution?

    Do we do an intermediate move to Core 3 now, or are we better off waiting until next year and jump straight to 5?

    Wednesday, October 23, 2019 7:36 AM

Answers

  • Hi Andy,

    Welcome to the MSDN forum.

    As far as l know, the .net core applications can cross platform no matter it is a window system or mac so that you do not worry about the platform on which the project will run. You can refer to this article about the differences between.net framework and.net core.

    ##With the advent of .Net Core 3 and now 5 around the corner, I was wondering whether we should be thinking about migrating our solution?

    >>It's largely up to your customers, and if your customers are using the windows operating system, you don't need to be migrating, and migrating from .net framwork to .net core is a complex and huge process. If your customers have a linux or mac operating system, you need to migrate your project. Specific migration steps you can refer to this document and need to use the command line and vs plug-in.

    ##Do we do an intermediate move to Core 3 now, or are we better off waiting until next year and jump straight to 5?

    >>.Net Core 3.0 has been officially launched, and if you have customers using mac, linux or other non-windows operating systems and they are in urgent need of buying and using your product, then you need to migrate this item to .net Core 3.0, although .net 5 it needs to be available in 2020 and looks like it has a significant improvement over .net core 3.0. 

    >>Information about .net 5 can be found in this:https://devblogs.microsoft.com/dotnet/introducing-net-5/#targetText=We%20intend%20to%20release%20.NET,5%20relates%20to%20.NET%20Framework.

    If you don't encounter this need until the .net 5 launch, you can migrate your framework project to .net 5.

    Any feedback will be expected.

    Best Regards,

    Perry



    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com


    Wednesday, October 23, 2019 10:18 AM