Share via

Re-built a winforms app from .net framework 4.7.2 to core 6.0 now questioning where to go next.

Steven Brewer 0 Reputation points
2026-01-12T16:07:11.3966667+00:00

So at work, we had a internal application that has been part of our key processes for the last 10 or so years and hasnt really received any big updates. The past two months I was given access to the source code and have pretty much started learning C# and winforms and updated all the libraries, cleaned out the old code, and such.

This application will likely never see use on any OS other than windows, it's just not likely. Is there good reason to go over to MAUI or WPF?

How have you all made public versions? Currently our plan is to work with IT and see about making a web application version on our website or trying another format. We would love to send it out to our partner agencies and they are really interested at being able to do the work themselves.

I figured I would ask the hive mind for thoughts.

Short version: Updated an old app my agency uses, now looking at next steps, Is MAUI or WPF worth the re-development? How have you all made public versions of an app?

Developer technologies | Windows Forms
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Bruce (SqlWork.com) 83,741 Reputation points
    2026-01-12T17:24:33.1766667+00:00

    Maui only supports windows and mobile, so switching only makes sense if a mobile app made sense. While WPF is newer than Winform, like WinForm it’s a stable library (not in active development). Microsoft does not have a good UI roadmap for windows, and even Maui uses dated technology.

    unless you are considering a web application instead of a desktop, I’d say you only need to upgrade to net 10. One disadvantage of .net core over the mature .net 4.* is you need to update every two years to the current version.

    0 comments
  2. Q&A Assist
    2026-01-12T16:07:20.4233333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Since you've already migrated your WinForms app to .NET Core 6.0, you have a solid foundation to build upon. Here are some considerations for your next steps:

    1. WPF: If you are looking for a more modern UI and want to take advantage of the latest design principles, WPF could be a good choice. It supports the Fluent theme, which aligns with the aesthetics of Windows 11, and provides features like integrated Light/Dark modes and system accent color support. However, if your application is primarily Windows-focused and you are comfortable with WinForms, you may not need to switch unless you want specific WPF features.
    2. MAUI: .NET Multi-platform App UI (MAUI) is designed for cross-platform development, but since you mentioned that your app will likely only be used on Windows, the benefits of MAUI may not be fully realized in your case. MAUI could be beneficial if you ever consider expanding to other platforms in the future.
    3. Public Versions: For making a public version of your app, consider creating a web application if your partners need remote access. This could involve using ASP.NET Core for the backend and a modern frontend framework. Alternatively, you could package your WinForms app as a desktop application for distribution, ensuring it meets the needs of your partner agencies.

    Ultimately, whether to migrate to WPF or MAUI depends on your specific requirements and future plans for the application. If you are satisfied with WinForms and it meets your needs, continuing to enhance it may be the best path forward.

    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.