.NET Framework vs .NET Core
15/02/2019 . 10 minutes, 26 seconds to read . Posted by Admin#MVCArchitecture #Model,View,Controller #htmlemail #codeigniteremail #XMLHandling #ViewsinCodeigniter #phpmyadmin
The .NET Framework
The .NET Framework supports Windows and Web applications. Today, you can use Windows Forms, WPF, and UWP to build Windows applications in .NET Framework. ASP.NET MVC is used to build Web applications in .NET Framework.
When to choose the .NET Framework
.NET Core offers significant benefits for new applications and application patterns. However, the .NET Framework continues to be the natural choice for many existing scenarios and as such the .NET Framework isn't replaced by .NET Core for all server applications.
Current .NET Framework applications
In most cases, you don’t need to migrate your existing applications to .NET Core. Instead, a recommended approach is to use .NET Core as you extend an existing application, such as writing a new web service in ASP.NET Core.
A need to use third-party .NET libraries or NuGet packages not available for .NET Core
Libraries are quickly embracing .NET Standard. .NET Standard enables sharing code across all .NET implementations including .NET Core. With .NET Standard 2.0, this is even easier:
· The API surface became much larger.
· Introduced a .NET Framework compatibility mode. This compatibility mode allows .NET Standard/.NET Core projects to reference .NET Framework libraries. To learn more about the compatibility mode, see Announcing .NET Standard 2.0.
So only in cases where the libraries or NuGet packages use technologies that aren't available in .NET Standard/.NET Core, you need to use the .NET Framework.
A need to use .NET technologies not available for .NET Core
Some .NET Framework technologies aren't available in .NET Core. Some of them might be available in later .NET Core releases. Others don’t apply to the new application patterns targeted by .NET Core and may never be available. The following list shows the most common technologies not found in .NET Core:
· ASP.NET Web Forms applications: ASP.NET Web Forms are only available in the .NET Framework. ASP.NET Core cannot be used for ASP.NET Web Forms. There are no plans to bring ASP.NET Web Forms to .NET Core.
· ASP.NET Web Pages applications: ASP.NET Web Pages aren't included in ASP.NET Core.
· WCF services implementation. Even when there’s a WCF-Client library to consume WCF services from .NET Core, WCF server implementation is currently only available in the .NET Framework. This scenario is not part of the current plan for .NET Core but it’s being considered for the future.
· Workflow-related services: Windows Workflow Foundation (WF), Workflow Services (WCF + WF in a single service) and WCF Data Services (formerly known as "ADO.NET Data Services") are only available in the .NET Framework. There are no plans to bring WF/WCF+WF/WCF Data Services to .NET Core.
· Language support: Visual Basic and F# are currently supported in .NET Core, but not for all project types.
A need to use a platform that doesn’t support .NET Core
Some Microsoft or third-party platforms don’t support .NET Core. Some Azure services provide an SDK not yet available for consumption on .NET Core. This is a transitional circumstance, as all of Azure services use .NET Core. In the meantime, you can always use the equivalent REST API instead of the client SDK.
It can be used with Docker and Windows Containers, and using it is most feasible when…
· You’re using third-party libraries or NuGet packages not available in .NET Core.While .NET Core is becoming more widely used, you’ll need to use the .NET Framework if you’re working with .NET Framework libraries that aren’t compatible. NuGet is the free and open source package manager for .NET and other Microsoft development platforms. The NuGet ecosystem includes client tools that provide the ability to produce and consume packages. It also has a central package repository for package authors and consumers. It is available as a Visual Studio extension.
· You’re using technologies not yet available in .NET Core
· It does not support all .NET Framework technologies. These not-yet-available technologies include:
o ASP.NET Web Forms applications (no plans to port)
o ASP.NET Web Pages applications (plans to port)
o ASP.NET Signal server/client implementation (plans to port)
o WCF services implementation (no plans to migrate, but it is being considered)
o Workflow related services (no plans to port) including Windows Workflow Foundation (WF), Workflow Services (WCF + WF in a single service), and WCF Data Services (formerly known as “ADO.NET Data Services”)
o Windows Presentation Foundation (WPF) and Windows Forms (no plans to port)
o Visual Basic and F# (both to be supported in Visual Studio 2017)
· The platform does not support .NET Core. Again, not all Microsoft and third-party platforms support it, such as some of Azure’s services. Many plan on adding support eventually, however. You may encounter some issues even with supported services, which, as developers, you know comes with the territory. With .NET Core increasingly gaining traction, it’s becoming easier to find tutorials and workarounds for issues you may encounter. For instance, we encountered a 502.5 Process Failure when trying to start an Azure App Service and wrote up a post offering guidance for others who encounter the same issue.
When Not to Run .NET Framework
There are also a few situations in which you shouldn’t run the .NET Framework, including when:
· Multiple OS platforms are required
· High performance and scalability are needed
· If .NET Core works
· Open source framework is required
.NET Core is the new open-source and cross-platform framework to build applications for all operating system including Windows, Mac, and Linux. .NET Core supports UWP and ASP.NET Core only. UWP is used to build Windows 10 targets Windows and mobile applications. ASP.NET Core is used to build browser based web applications.
.NET Core has the following characteristics:
· Cross-platform: Runs on Windows, macOS and Linux operating systems.
· Consistent across architectures: Runs your code with the same behavior on multiple architectures, including x64, x86, and ARM.
· Command-line tools: Includes easy-to-use command-line tools that can be used for local development and in continuous-integration scenarios.
· Flexible deployment: Can be included in your app or installed side-by-side user- or machine-wide. Can be used with Docker containers.
· Compatible: .NET Core is compatible with .NET Framework, Xamarin and Mono, via .NET Standard.
· Open source: The .NET Core platform is open source, using MIT and Apache 2 licenses. .NET Core is a .NET Foundation project.
· Supported by Microsoft: .NET Core is supported by Microsoft, per .NET Core Support.
When to choose .NET Core
· There are cross-platform needs. Use it when the application needs to run across multiple platforms such as Windows, Linux and macOS. Those operating systems are supported as development workstations (and the list of supported operating systems is growing):
o Visual Studio can be used on Windows with a new limited version on the macOS.
o Visual Studio Code can be used on Windows, Linux and macOS.
o The command line can be used on all supported platforms.
· Microservices are being used. Microservices, a form of service-oriented architecture, are software applications comprised of small, modular business services. Each service can run a unique process, be deployed independently and be created in different programming applications. .NET Core allows a mix of technologies, is lightweight and can be minimized for each microservice. It is scalable as new microservices are added.
· When Docker containers are being used. Containers and microservices architecture often are used together. Because it is lightweight and modular, .NET Core works very well with containers. Server apps can be deployed cross-platform to Docker containers. .NET Framework can be used for containers, but the image size is larger.
· If you have high performance and scalable system needs. Microsoft recommends running .NET Core with ASP.NET Core for the best performance and scale. This becomes important when hundreds of microservices could be used. A lower number of servers and virtual machines should be needed. The efficiency and scalability gained could translate to a better user experience in addition to cost savings.
· If you are running multiple .NET versions side-by-side. To install applications with dependencies on different versions of frameworks in .NET, developers need to use .NET Core. Multiple services can be run on the same server with different versions of .NET.
· If you want command line interface (CLI) control. Some developers prefer working in lightweight editors and command line control. .NET Core has a CLI for all supported platforms. It requires minimal installation on production machines. And there still is the opportunity to switch to an IDE such as Visual Studio IDE.
When Not to Run .NET Core
One issue is that it does not have some .NET features or support all libraries and extensions. There are a few situations in which it may not (currently) be the best option, although, with continued development, it will likely be workable for most use cases eventually. Consider the following scenarios:
· Windows Forms and WPF applications are not supported. You still have to use mono to make a .NET desktop application for macOS.
· ASP.NET WebForms don’t exist. Microsoft has plans to port them to ASP.NET Core either.
· You need to create a WCF service. .NET Core does not currently support WCF. Instead, you would need to make a REST API with ASP.NET Core MVC.
· Missing 3rd party library support. .NET Core 2.0 provides a compatibility shim between .NET Framework and .NET Core. But, you may still have issues with compatibility if the class library uses any .NET Framework APIs that are not supported. Although, this will help bridge a lot of class libraries to .NET Core.
· Missing .NET Framework features. Some .NET Framework functionality is still missing in .NET Core. For example, Entity Framework Core is not the exact same as Entity Framework v6.
· You need to access Windows specific APIs. If your application needs to work with the Windows Registry, WMI, or other Windows specific APIs, it won’t work with .NET Core. It is designed to be more sandboxed away from the OS.
Memory management
Type and memory safety
Security
Networking