4 ms·
What I still don't understand in this picture is the what does the future look like in terms of the .NET framework. .NET Core sounds great, and its great that
by Eyas 12y ago
What I still don't understand in this picture is the what does the future look like in terms of the .NET framework.
.NET Core sounds great, and its great that they are unifying the implementation, not just the API, for many of the "app models". But, its unclear to me if there's the intention for .NET Core to fully succeed .NET Framework at some point in the future. Or, rather, will some of the app models we see on top of the Framework right now (WinForms, WPF apps) be built with .NET Core in some future version?
- cpayne 12y agoI think the reason why the future isn't spelt out is because they don't know (or haven't decided). The last 12 months have been massive steps for Microsoft (open source, multi platform). I would expect they would wait and see how their customers & community react. Also Azure is a massive component to all of this (they make money of Azure, they don't make a massive amount of cash from someone using .Net). Microsoft have a long history of keeping old versions alive (unlike say Apple). Eg Internet Explorer, Windows XP, Office, Win Forms vs MVC I'm sure .Net core will take over one day. In the same way .Net 4.5 overtook .Net 2 / 1.1 etc.
- stinos 12y agoI'm wondering the exact same thing. What is the relationship between the two? How easy is it to bridge them or is that not possible? I mean suppose I want to write some typical backend utility code like extensions for collections etc: can the same code for .NET framework be used for .NET core? Eventually with some #ifdefs?