.NET Core - Modularity


It is another consideration of .NET Core to build and implement application that is modular. Instead of installing the entire .NET Framework, your application can now just install what is required. Let us go to the visual studio and see the modularity.

Here is our simple .NET Core application, in Solution Explorer. Let us expand References and you will see reference to .NETCoreApp

.Net Core App

Inside .NETCoreApp, you will see package reference to NuGet; let us expand it.


You will see the whole series of NuGet Package references. If you have worked in .NET Framework, then many of these namespaces will look familiar, because you are used to it by using in .NET Framework.

.NET Framework is split into many different pieces and re-implemented with CoreFx; these pieces are further distributed as individual packages.

  • Now if you expand the NETStandard.Library, you will see addition references. You will even notice System.Console which we are using in this application.

  • Now you don’t have to bring in everything inside the .NET Framework, but just bring in what you need for your application.

  • There are some other benefits as well; for example, these modules can be updated individually if desired.

Modularity leads to performance benefits and your application can run faster, especially ASP.NET Core application.