How To Port To .NET Core?In this blog,we tried to simplify the porting effort by unifying the core APIs with

other .NET platforms, mainly the .NET Framework and Mono/Xamarin.

Introduction

The .NET Core platform developed to design a modern, modular and cross-

platform .NET stack. The business goals were focused on providing a stack for

brand new application types or modern cross-platform applications.

While .NET Core works good for the situations that we set out to address, it

provides access to a few technologies than other .NET platforms, mainly the

.NET Framework.

It became clear that adopting .NET Core would require existing .NET developers

to spend a certain amount of time to port to it.

Xamarin is a great role model . They allow .NET developers to build mobile

applications for the iOS and Androids with minimal effort. iOS shares many of

the characteristics of the UWP platform, such as the high focus on end-user

experience and the need of static compilation. But, in contrast to .NET Core,

Xamarin did not start with re-imagining the .NET stack. They took Mono as tis,

removed the application model components, added a new one for iOS, and

made a few changes to make it suitable for embedding.

Since the beginning, the key promise of .NET was to make developers more

productive and help them write robust code. It was created from the start to

support developers on a wide range of areas starting with desktop and web

applications to mobile applications, microservices, and gaming.

For us to deliver ,it is critical that we give a unified core API that is available

everywhere. A unified core API permits developers to easily share code across

these workloads and allows them to define their skills where it matters the

most – creating good services and user experiences.

.NET Core moving forward

Whether you need to build a mobile app, desktop application,a website, or a

micro service: you can rely on .NET to get you there. Code sharing has become

very easy because of unified BCL. As a developer, you can focus on the

attributes and technologies that are specific to the user experiences and

platforms you’re opting for.

Whether you aim the .NET Core 1.0 surface (System.Runtime-based surface), or

the upcoming version of .NET Core with the expanded API (mscorlib-based

surface), your existing code will continue to function.

The promise of bringing existing code extends to libraries and NuGet packages

with an ease. This also includes portable class libraries, regardless of whether

they used mscorlib or System.Runtime.

Here are examples of the additions that will make your life easier when

targeting to .NET Core:

Reflection will be the same as .NET Framework, no need for GetTypeInfo(), good

old .GetType() is back.

Types will no longer miss members that have been removed for clean up

reasons (Clone(), Close() vs Dispose(), old APM APIs)

Binary serialization (BinaryFormatter) will be again available.

From various discussions, on social media, it seems there is a concern that

these API additions degrade the .NET Core experience.

The same is true for all additional features and performance improvements

made, such as the new networking component called Kestrel.

Originally,NET Core was designed, there was talk about modularization and pay

for play, meaning you only have to consume the disk space for the features

that you end up using. The fact is that we can still realize these goals without

compromising so heavily on compatibility.

The process to extend the API surface of .NET Core will come after the

shipment of .NET Core 1.0 RTM.

Lastly, plans are there to release incremental updates to .NET Core on NuGet

that extends the set of available APIs. This way, developers will not have to

wait until all the API additions are done in order to take advantage of them.

Stay connected for more details!

If you are interested in learning ASP.Net and perfecting yourself in .NET

training, then CRB Tech Solutions would be very helpful. We update ourselves

with the current developments in ASP.Net course.

Stay connected to the page of CRB Tech reviewsfor more technical optimization

and other resources.

Related Articles:

Here Are Few Tips on Asp.Net Life Cycle

Importance of Asp.Net Development