Comparison of .NET Core and .NET Framework
Category |
.NET Core |
.NET
Framework |
Open source |
.Net Core is an
open source. |
.NET Frame work is
not open source. Some components are open source. |
Cross-Platform |
.NET Core is cross-platform, and supports three
distinct operating systems — Windows, OS X, and Linux. |
.NET Framework enabled developers to build
applications for a single platform — Windows. |
Application Models |
.Net Core focuses more on Web, Windows
Mobile, and Windows Store applications. |
.Net Framework is used to build both
Desktop as well as Web applications. |
Installation |
.NET Core is packaged and installed independently
of the underlying operating system as it is cross-platform. |
.NET Framework is installed as a single package
for Windows operating system. |
Framework |
.Net Core is a platform on top of
which there are frameworks such as ASP .Net Core and Universal Windows
Platform that leverage and extend the features of .Net Core. |
.Net Framework is a full-fledged
development framework. It provides UI, DB connectivity, Services, APIs, etc. |
Performance
and Scalability |
.NET
Core is more effective than .NET Framework to enhance the performance and
scalability of applications. It enables developers to enhance the performance
of applications drastically without deploying additional hardware or
infrastructure. Also, it allows developers to build, test and deploy
applications directly in the cloud. Hence, the developers can switch to .NET
Core to enhance the performance and scalability of their applications without
putting extra time and effort |
.Net
Framework is less effective in comparison to .Net Core in terms of
performance and scalability of applicatio |
Micro-Services |
.NET Core makes it easier for
developers to build microservice oriented systems rapidly. .NET Core enables
programmers to develop custom microservices by using varying programming
languages, technologies and frameworks. Also, the developers can build a
robust system by combining multiple microservices seamlessly. |
.Net Framework does not support the
development and implementation of microservices but it supports the REST API
services. |
Compatibility |
.NET
Core is compatible with various operating systems — Windows, Linux, and Mac
OS. .NET Core does not support all the features and functionalities provided
by the latest version of .NET Framework. But it can be used as a subset of
the .NET Framework. |
.NET
Framework is compatible only with the Windows operating system. |
Packaging and Shipping |
.Net Core is delivered as a set of
NuGet packages. It has been factored, modularized and shipped as several
NuGet packages. |
.Net Framework is packaged as a whole.
All the libraries are bundled together and shipped together. |
WCF/REST
Services |
.Net
Core has no support for WCF services. You would always need to create a REST
API. |
.Net
Framework is an excellent choice when WCF services are involved. It also
supports REST services. |
CLI Tools |
.Net Core supports a very lightweight
CLI for all platforms. There is always an option to switch to an IDE as well. |
.Net Framework is too heavy for
Command Line Interface. |
Mobile
App Development |
.NET Framework does not include any robust
framework or tools to simplify mobile app development. |
.NET Core compatible with Xamarin through the
.NET Standard Library. Hence, developers can take advantage of Xamarin to
write cross-platform mobile apps in C# with a shared code base and same set
of APIs. They can further use the tools provided by Xamarin to customize the
mobile app for individual mobile platforms like iOS, Android and Windows
Phone. |
Cloud Ready Configuration |
.NET Core is designed with features to
simplify development and deployment of cloud-based application. |
It is not easy to deploy in cloud |
Deployment
Model |
Whenever
the updated version of .NET Core gets initiated; it is updated instantly on
one machine at a time, thereby getting updated in new directories/folders in
the existing application without affecting it. Thus, .NET Core has a good and
flexible deployment model. |
In
the case of .Net Framework, when the updated version is released it is first
deployed on the Internet Information Server only. |
Standard Library |
.NET Core
implements version 1.6 of the .NET Standard Library. |
s a formal
specification of .NET APIs, the .NET Standard Library meets the requirements
of varying runtimes and maintains uniformity in the .NET ecosystem. Each
version of .NET Framework uses a specific version of .NET Standard Library.
For instance, .NET Framework 4.6 implemented the .NET Standard Library 1.3 |
Modular
Collection of Libraries |
.NET Core uses a redesigned common language
runtime called CoreCLR, and features a modular collection of libraries called
CoreFX. Hence, the developers have option to pick and use only the libraries
required by each application, and enhance the application’s performance by
removing unnecessary libraries. |
.NET Framework and .NET Core allows developers to
take advantage of robust class libraries. |
.net framework vs .net core |
No comments:
Post a Comment