6 ms·

Legacy net framework Will stop with 4.8, as said some months ago EDIT: more on this here https://devblogs.microsoft.com/dotnet/update-on-net-core-3-0-and-net-f

Legacy net framework Will stop with 4.8, as said some months ago EDIT: more on this here https://devblogs.microsoft.com/dotnet/update-on-net-core-3-0-and-net-framework-4-8/ https://devblogs.microsoft.com/dotnet/update-on-net-core-3-0...

lol768 7y ago
Fair enough - but the wealth of documentation for it will continue to exist, as will older applications targetting it. This seems problematic if you want to search for ".NET" (meaning .NET Core).
cm2187 7y ago
I missed that, and that would be a pretty big deal. I thought the message was of a side by side evolution, with full framework getting features possibly with a delay.
- manigandham 7y ago
  There's no point since .NET Core 3.0 can run desktop applications now.
  - lol768 7y ago
    All the desktop stuff is only on Windows though, right? If I'm not mistaken this is the first major .NET Core component that is not cross-platform, which is confusing in itself.
    - manigandham 7y ago
      Yes, since it's using Windows components like WPF. I dont think they ever had a plan for a cross-platform desktop UI kit.
      - solarkraft 7y ago
        They explicitly won't support cross-platform efforts for the GUI stuff, as stated on GitHub (though maybe, one day ...). I suppose their rationale is damage control ("Okay, they get the server, but the desktop is still firmly ours"), but it would certainly keep me from starting a personal project with a Microsoft Framework.
        MikeTheGreat 7y ago
        > but the desktop is still firmly ours At this point I'm guessing that it's because there isn't a strong future for desktop apps written in native code. Even VSCode is written on top of Electron. Good, bad, or indifferent I think that there isn't a lot of point in developing a native GUI framework at this point. (To be clear - I'm 100% sure that there are a lot of use cases that I'm blithely waving away, but I'm also sure that those use cases are currently being addressed with WinForms, Qt, GNOME, etc, etc, so why should MS invest in Yet Another GUI Framework?)
        tracker1 7y ago
        I wouldn't mind seeing WPF, or a descendent, ported to other platforms. Xamarin Forms, Eto Forms, and a lot of other wrappers already do a lot of that though, if you want cross platform gui from .Net. (god that looks sloppy) I also tend to agree that for good, or bad, that Electron will probably grow significantly as an application base. Like I see node becoming the defacto runtime for WebAssembly, I see Electron taking that place for WebAssembly + UI. And I don't think it's all that bad. Even with MS, Electron seems to be their unified UI target for a lot of apps. VS Code, Teams, Azure SQL Studio (or whatever the name is now), and don't see that space shrinking. I'm only surprised that Teams doesn't have an official Linux version.
        jodrellblank 7y ago
        WinForms is outdated, "replaced" by WPF and I think apps on the Microsoft App Store have to use WPF instead of WinForms. So it would make sense if they're pushing .Net Core to be cross-platform, that they want to eventually push the Microsoft App Store "buy" button to be cross-platform as well, with a GUI framework to support those apps. Speculation, but .. of course they will want to.
  - cm2187 7y ago
    It will run desktop applications developped for .net core. I don't believe that .net core can run a full framework desktop executable.
    - testvox 7y ago
      It can using the compatibility shim depending on what framework capabilities it requires.
      - pjmlp 7y ago
        WCF, Remoting, Web Forms, ODP.NET, EF6 UI designers certainly not. Yes, some of those items are legacy, but not everyone enjoys paying to rewrite stuff from scratch.
  - pjmlp 7y ago
    Only partially, try to run any desktop application that depends on WCF or ODP.NET with it.
    - merb 7y ago
      wcf works under core (at least most of it), core 3.0 + wcf + windows desktop shim actually makes everything under wcf working again.
      - pjmlp 7y ago
        Most of it is not good enough. I don't want to be the one stating on RFP "it kind of works".
        manigandham 7y ago
        What is not good enough?
        pjmlp 7y ago
        Pick random .NET app using WCF and run it with zero changes on .NET Core.
        cwyers 7y ago
        The implication I took from this was that it's not good enough now, but they anticipate it being good enough by the point this is released.
        pjmlp 7y ago
        Those customers want the existing apps to just run. Some of them, as sometimes happens, don't want to rewrite them.
- WorldMaker 7y ago
  Key pull quotes in this article specifically: > There will be just one .NET going forward > Additionally, we wanted to clearly communicate that .NET 5 is the future for the .NET platform.
  - cm2187 7y ago
    Well, it is not really the case, there will be still two frameworks, just one isn't going to be developped anymore (full .net 4.8). The way I read that sentence initially was them merging the two into one.
    - coldtea 7y ago
      >Well, it is not really the case, there will be still two frameworks, just one isn't going to be developped anymore (full .net 4.8). If "one isn't going to be developed anymore" there there will be just one framework. "Being" here means what's the official worked-on implementation. Not merely existing, obviously the code for 4.8 wont go anywhere, nor will existing deployments suddenly vanish.
      - cm2187 7y ago
        When 4.8 is installed, 4.7 is going away. Here .net 5 will not replace .net 4.8, it will exist side by side (if I understand correctly). That's two frameworks to me.
        ticmasta 7y ago
        >> When 4.8 is installed, 4.7 is going away. That's not true at all. You can run any version of the framework side-by-side all the way back.
        cheerlessbog 7y ago
        You can only have a single 4.x version on the box. They all install into the same folder.
james_s_tayler 7y ago
But that article says: "Both .NET Framework and .NET Core will move forward, and both will be fully supported" ??? Which is why I found this one confusing... because it essentially says the opposite.
- D_Guidi 7y ago
  Yep, I've semplified. What I understood from this post is that net framework is in "maintenance mode": probably MS plan a 4.8.1 with but fixes and maybe a 4.9 with some minor updates, but .net core (now simply .net) is the place where new things will be developed.
  - brianberns 7y ago
    I don’t see anything in the linked article that supports your conclusion.
    - tracker1 7y ago
      Nothing in the article suggests maintenance releases, but MS' history is probably enough for that. The article does definitely state that .Net 5 is the evolution of Core and will be the entire platform going forward. I'm, personally, glad to see Core/Framework/Mono etc rolled into a single version at 5. The previous split versions have been fairly confusing.
    - D_Guidi 7y ago
      yep! this blog post is more clear about future releases: https://devblogs.microsoft.com/dotnet/net-core-is-the-future-of-net/ https://devblogs.microsoft.com/dotnet/net-core-is-the-future... "We will continue to both service and support .NET Framework, which includes bug–, reliability– and security fixes."
  - runfaster2000 7y ago
    Here is the post you are looking for, I think ... https://devblogs.microsoft.com/dotnet/net-core-is-the-future-of-net/ https://devblogs.microsoft.com/dotnet/net-core-is-the-future...

lol768 7y ago

Fair enough - but the wealth of documentation for it will continue to exist, as will older applications targetting it. This seems problematic if you want to search for ".NET" (meaning .NET Core).

cm2187 7y ago

I missed that, and that would be a pretty big deal. I thought the message was of a side by side evolution, with full framework getting features possibly with a delay.

manigandham 7y ago
There's no point since .NET Core 3.0 can run desktop applications now.
- lol768 7y ago
  All the desktop stuff is only on Windows though, right? If I'm not mistaken this is the first major .NET Core component that is not cross-platform, which is confusing in itself.
  - manigandham 7y ago
    Yes, since it's using Windows components like WPF. I dont think they ever had a plan for a cross-platform desktop UI kit.
    - solarkraft 7y ago
      They explicitly won't support cross-platform efforts for the GUI stuff, as stated on GitHub (though maybe, one day ...). I suppose their rationale is damage control ("Okay, they get the server, but the desktop is still firmly ours"), but it would certainly keep me from starting a personal project with a Microsoft Framework.
      - MikeTheGreat 7y ago
        > but the desktop is still firmly ours At this point I'm guessing that it's because there isn't a strong future for desktop apps written in native code. Even VSCode is written on top of Electron. Good, bad, or indifferent I think that there isn't a lot of point in developing a native GUI framework at this point. (To be clear - I'm 100% sure that there are a lot of use cases that I'm blithely waving away, but I'm also sure that those use cases are currently being addressed with WinForms, Qt, GNOME, etc, etc, so why should MS invest in Yet Another GUI Framework?)
        tracker1 7y ago
        I wouldn't mind seeing WPF, or a descendent, ported to other platforms. Xamarin Forms, Eto Forms, and a lot of other wrappers already do a lot of that though, if you want cross platform gui from .Net. (god that looks sloppy) I also tend to agree that for good, or bad, that Electron will probably grow significantly as an application base. Like I see node becoming the defacto runtime for WebAssembly, I see Electron taking that place for WebAssembly + UI. And I don't think it's all that bad. Even with MS, Electron seems to be their unified UI target for a lot of apps. VS Code, Teams, Azure SQL Studio (or whatever the name is now), and don't see that space shrinking. I'm only surprised that Teams doesn't have an official Linux version.
        jodrellblank 7y ago
        WinForms is outdated, "replaced" by WPF and I think apps on the Microsoft App Store have to use WPF instead of WinForms. So it would make sense if they're pushing .Net Core to be cross-platform, that they want to eventually push the Microsoft App Store "buy" button to be cross-platform as well, with a GUI framework to support those apps. Speculation, but .. of course they will want to.
- cm2187 7y ago
  It will run desktop applications developped for .net core. I don't believe that .net core can run a full framework desktop executable.
  - testvox 7y ago
    It can using the compatibility shim depending on what framework capabilities it requires.
    - pjmlp 7y ago
      WCF, Remoting, Web Forms, ODP.NET, EF6 UI designers certainly not. Yes, some of those items are legacy, but not everyone enjoys paying to rewrite stuff from scratch.
- pjmlp 7y ago
  Only partially, try to run any desktop application that depends on WCF or ODP.NET with it.
  - merb 7y ago
    wcf works under core (at least most of it), core 3.0 + wcf + windows desktop shim actually makes everything under wcf working again.
    - pjmlp 7y ago
      Most of it is not good enough. I don't want to be the one stating on RFP "it kind of works".
      - manigandham 7y ago
        What is not good enough?
        pjmlp 7y ago
        Pick random .NET app using WCF and run it with zero changes on .NET Core.
      - cwyers 7y ago
        The implication I took from this was that it's not good enough now, but they anticipate it being good enough by the point this is released.
        pjmlp 7y ago
        Those customers want the existing apps to just run. Some of them, as sometimes happens, don't want to rewrite them.
WorldMaker 7y ago
Key pull quotes in this article specifically: > There will be just one .NET going forward > Additionally, we wanted to clearly communicate that .NET 5 is the future for the .NET platform.
- cm2187 7y ago
  Well, it is not really the case, there will be still two frameworks, just one isn't going to be developped anymore (full .net 4.8). The way I read that sentence initially was them merging the two into one.
  - coldtea 7y ago
    >Well, it is not really the case, there will be still two frameworks, just one isn't going to be developped anymore (full .net 4.8). If "one isn't going to be developed anymore" there there will be just one framework. "Being" here means what's the official worked-on implementation. Not merely existing, obviously the code for 4.8 wont go anywhere, nor will existing deployments suddenly vanish.
    - cm2187 7y ago
      When 4.8 is installed, 4.7 is going away. Here .net 5 will not replace .net 4.8, it will exist side by side (if I understand correctly). That's two frameworks to me.
      - ticmasta 7y ago
        >> When 4.8 is installed, 4.7 is going away. That's not true at all. You can run any version of the framework side-by-side all the way back.
        cheerlessbog 7y ago
        You can only have a single 4.x version on the box. They all install into the same folder.

james_s_tayler 7y ago

But that article says: "Both .NET Framework and .NET Core will move forward, and both will be fully supported" ??? Which is why I found this one confusing... because it essentially says the opposite.

D_Guidi 7y ago
Yep, I've semplified. What I understood from this post is that net framework is in "maintenance mode": probably MS plan a 4.8.1 with but fixes and maybe a 4.9 with some minor updates, but .net core (now simply .net) is the place where new things will be developed.
- brianberns 7y ago
  I don’t see anything in the linked article that supports your conclusion.
  - tracker1 7y ago
    Nothing in the article suggests maintenance releases, but MS' history is probably enough for that. The article does definitely state that .Net 5 is the evolution of Core and will be the entire platform going forward. I'm, personally, glad to see Core/Framework/Mono etc rolled into a single version at 5. The previous split versions have been fairly confusing.
  - D_Guidi 7y ago
    yep! this blog post is more clear about future releases: https://devblogs.microsoft.com/dotnet/net-core-is-the-future-of-net/ https://devblogs.microsoft.com/dotnet/net-core-is-the-future... "We will continue to both service and support .NET Framework, which includes bug–, reliability– and security fixes."
- runfaster2000 7y ago
  Here is the post you are looking for, I think ... https://devblogs.microsoft.com/dotnet/net-core-is-the-future-of-net/ https://devblogs.microsoft.com/dotnet/net-core-is-the-future...