The good, the bad and the ugly – We look at .NET Core and ASP.NET Core 1.0 changes
In January Microsoft announced a huge change in the .net world – ASP.NET 5.0 had been rechristened as ASP.NET Core 1.0. Microsoft’s Scott Hanselman explained on in his blog “… naming the new, completely written from scratch ASP.NET framework "ASP.NET 5" was a bad idea for one major reason: 5 > 4.6 makes it seem like ASP.NET 5 is bigger, better, and replaces ASP.NET 4.6. Not so.” In fact, the ASP.NET Core 1.0 is a more a brand new platform and not just an upgrade from the earlier version like ASP.NET 3 and 4. Written from scratch to its core to help build applications, it rightly deserved a new name.
The .NET Core 1.0 naturally has much about it to be discussed and for most part appreciated. Here are few changes that make this one a winner.
It is Open Source
A major shift in the .NET Core is that Microsoft is open-sourcing the .NET Core packages on GitHub. The .NET Core has been built to be moveable across platforms. This helps accommodate code reuse and sharing. In order to make the .NET open source Microsoft trimmed it down to be more agile. Being open sourced means a whole lot of benefits for the technology - the community can better it with recommended changes constantly. .Net developers can now have quicker updates.
The .NET Core is a modular version of .NET Framework that can now be used across platforms. Even though .NET Core is part of .NET Framework, it now has key functionality to implement the app features, and one can utilise this code repeatedly on any platform.
Earlier various versions of .NET for different platforms didn’t have shared functionality for some tasks - such as reading local files. With the .NET Core one can target The traditional windows devices, phones, desktops, yes, but it will also be portable to IOS and Android devices. It will also be available for the Mac and Linux operating systems soon. This development is definitely welcome.
NET.Core is smaller and has feature-centric packages. It isn’t one assembly with most of the core functionality. So now one has the luxury of choosing the functionality pieces that are needed for one’s apps and libraries.
A Few Limitations
However, there are some curbs in the ASP.NET Core 1.0. It includes Asp.NET Web API and MVC but doesn't yet have SignalR or Web Pages. Currently, it also doesn't yet support VB or F#. We also need to remember that there is a lack of documentation and unknown features at this point and asp.net 1.0 is not yet a finished product
Manjunath Govindappa | ASP.NET Technical Lead
Elizabeth Raj | Blogger