| Compatibility | It works based on the principle of “build once, run ANYWHERE”. It is cross-platform, so it is compatible with different operating SYSTEMS such as Linux, Windows, and Mac OS. | This framework is compatible with the Windows operating system only. Even though, it was developed for supporting software and applications on all operating systems. |
|---|
| Installation | Since it is cross-platform, it is packaged and installed independently of the OS. | It is installed in the FORM of a single package for Windows OS. |
|---|
| Application Models | It does not support developing the desktop application and it focuses mainly on the windows mobile, web, and windows store. | It is used for developing both desktop and web applications, along with that it also supports windows forms and WPF applications. |
|---|
| Performance and Scalability | It provides high performance and scalability. | It is less effective compared to .Net Core in terms of performance as well as scalability of applications. |
|---|
| Support for Micro-Services and REST Services | It supports developing and implementing the micro-services and the user is REQUIRED to create a REST API for its implementation. | It does not support the microservices’ development and implementation, but it supports REST API services. |
|---|
| Packaging and Shipping | It is shipped as a collection of Nugget packages. | All the LIBRARIES that belong to the .Net Framework are packaged and shipped all at once. |
|---|
| Android Development | It is compatible with open-source mobile app platforms like Xamarin, via .NET Standard Library. Developers can make use of tools of Xamarin for configuring the mobile application for particular mobile devices like Android, iOS, and Windows phones. | It does not support the development of mobile applications. |
|---|
| CLI Tools | For all supported platforms, it provides lightweight editors along with command-line tools. | This framework is heavy for CLI(Command Line Interface) and developers usually prefer to work on the lightweight CLI. |
|---|
| Deployment Model | Updated version of the .NET Core gets initiated on one machine at a time, which means it gets updated in new folders/directories in the existing application without affecting it. Thus, we can say that .NET Core has a very good flexible deployment model. | When the updated version is released, it is deployed only on the Internet Information Server at first. |
|---|
