Traditional Framework Takes Back Seat to Core RRS feed

  • General discussion

  • Good read

    Microsoft's shift from the traditional 16-year-old .NET Framework to modernized "Core" implementations is picking up in pace.

    With the .NET Framework introduced in 2002 so closely tied to Windows, Microsoft needed to make some changes in its new era of openness and interoperability, so in 2016 it debuted its Core versions, which are open source and cross platform, running on macOS and Linux in addition to Windows.

    As the initial Core offerings (along with .NET Standard, which specs out what APIs all .NET implementations should support) lacked some robustness and functionality, Microsoft was guarded in its migration advice at first.

    For example, less than a year ago, the company's Immo Landwerth said "So there are good reasons why you may not want to port to .NET Core."

    He continued: "Depending on what you're doing, if you're building a Windows Forms app or UWP apps or using WebForms apps, you probably should not port to .NET Core yet because the .NET Framework is still the best bet that you can take."

    Since then, all that has changed.

    Please remember to mark the replies as answers if they help and unmark them if they provide no help, this will help others who are looking for solutions to the same or similar problem. Contact via my Twitter (Karen Payne) or Facebook (Karen Payne) via my MSDN profile but will not answer coding question on either.
    VB Forums - moderator
    profile for Karen Payne on Stack Exchange, a network of free, community-driven Q&A sites

    Thursday, October 25, 2018 2:09 PM