When to decide To Use ASP.NET Core 2.0 or 2.2

How i decide when to use Asp .net core 2.0/2.2 – By Sagar Jaybhay

After having seen the varied options and functionalities provided by ASP.NET Core 2.0, you may raise yourself if it’ll replace the total classic .NET Framework in the future.

It’s true that ASP.NET Core 2.0 and therefore the underlying .NET Core Framework give some major improvement and performance enhancements, but there are still some specific situations, wherever those new application patterns don’t apply and wherever the total .NET Framework are the simplest and generally even the only alternative.

Migrating your whole existing applications to ASP.NET Core right from the beginning might be tough or perhaps not possible to try and do. 

You must deem a way to rework your applications increasingly to lower the chance of failure or over-simplification and give yourself time to essentially perceive the new patterns and paradigms.

You could begin as an example by solely exploitation ASP.NET Core 2.0 for all new developments, then see a way to migrate your legacy code later and generally even leave it’s since there’ll be no real advantages for migrating it over.

ASP.NET Core and therefore the .NET Core Framework get additional and additional framework and client library support every day. 

Microsoft, tool and framework vendors, and the different developer communities work effortlessly to produce an outsized set of functionalities for permitting feature-rich and high performing arts web applications.

Everyone desires to work on this promising technology that might form the long run during a property method. The possibility to use .NET Core and .NET Framework libraries along at an equivalent time once using .NET normal two.

When to decide To Use ASP.NET Core 2.0 or 2.2

0 extends the chances even additional and offers developers a brief answer till each necessary feature and each major framework are accessible in .NET Core.

Points to decide:

  1. You have cross-platform desires
  2. You are specifically targeting micro services
  3. You want to use docker containers
  4. You need high performance and extremely scalable applications
  5. You need to place multiple applications with totally different .NET versions facet by facet
  6. The given technical restrictions don’t apply to your application requirements

Audio Link: –



You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *