Microsoft to bury .Net Framework

Notice, I have this information from a credible inside source, and no I won’t tell you who. However, apparently Microsoft has plans to bury .Net Framework as of version 4.8. This means that version 4.8 will be the last update to .Net Framework to ever be released by Microsoft.

Apparently all focus is on .Net Core in the future. The reasons I assume is that .Net Core is platform agnostic, and Microsoft apparently no longer have an interest in creating lockins towards their own Windows systems. However, think about the ramifications of this for a while …

For instance, no more WCF, no more WPF, no more WinForms, no more WebForms, the list goes on …

Personally, I must admit I have mixed feelings to this. On the one hand, there’s a millions methods and classes I have grown accustomed to in .Net Framework, which simply does not have an equivalent in .Net Core. At the same time, I love the idea of cross platform development, and every time I have to mess with Mono to get my stuff working, it seems to create head aches for me. I also adore the modularity of .Net Core, which is in extreme contrast to the monolithic nightmare of .Net Framework …

However, .Net Framework will be killed by Microsoft, and the last major upgrade will be version 4.8. How they intend to do it, and if they intend to create security releases for a decade or so, fixing security holes the way they usually do when they snuff their own stuff, I don’t know. But one thing is certain, if you’ve got intellectual investments on .Net Framework today, you’d better start reading up on .Net Core – Otherwise I assume you’ll end up as the dinosaurs …


11 thoughts on “Microsoft to bury .Net Framework

  1. I think you are misinformed about the following statement;

    “For instance, no more WCF, no more WPF, no more WinForms, no more WebForms, the list goes on …”

    These services and frameworks are already beginning their journey over to the platform agnostic side. If I’m correct, we’ll a few of these technologies in .net core 3.

    Liked by 1 person

  2. They announced announced WPF for .net Core 3.0 coming next year so they’re not getting rid of the whole stack. In fact this will be the first windows only addition to Core.
    They probably realized how cumbersome it becomes to have backwards compatibility when you’re entire runtime has to support code written on VS 2010, instead of just bundling the libraries with the application (which is how the .Net Core version will work).

    Liked by 1 person

  3. I’m not sure how much to trust your source considering your statements about Winforms and WPF. Dotnet Core 3.0 is supposed to support them just fine. It won’t be cross platform due to the deep Windows dependencies, but they aren’t going to abandon all UI kits. That said, it makes the transition far easier for Microsoft. This article also comes immediately after Microsoft posted that they have a number of product lines on framework with zero plans to migrate them to anything else and will continue to develop framework. Perhaps your sources correct and you simply hadn’t heard about some of the Winforms and WPF plans, but I imagine sunsetting the runtime will take more than a decade.


  4. I believe Microsoft will kill the NET framework, but not in your statement that this will mean no more WPF or Windows Forms.

    This is because NET Core 3.0 will in fact support WPF and Windows Forms.

    Liked by 1 person

  5. These were my additions after having played around with .Net Core a while, and realising everything that was (still) missing. WCF I had to completely give up on for instance. However, (obviously) some of these missing things, hopefully most of them, will find their way into .Net Core before they bury .Net Framework I assume …


  6. Yet again, the comments about WCF etc was my additions after having played around with .Net Core. However, my source is extremely credible, and arguably if you stop and think about it for some time, it’s madness to keep both .Net Core and .Net Framework around …


  7. It’s even more madness to not give your customers and enterprise customers an upgrade path, something that Microsoft has insisted on since forever for almost all of their products.

    Even if that means covering all of this by supporting it in NET Core first, and then removing the NET Framework, there will always be an upgrade path, and the point of the article is not really that interesting in my opinion, because no one gets hurt in that process.

    Liked by 1 person

  8. I agree on that no one gets hurt. In a way, I look at this as cause for celebration, since it implies all their muscles will be targeting .Net Core …

    However, the pain when a “king dies” and his “son takes over” is always there though …


Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.