Welcome to the series of asp.net core tutorials, in this part we will discuss another new feature that has shipped with asp.net core 2.0

Let’s first discuss 2 problems faced by monolithic applications:

• All packages need to be deployed for application to run correctly and for different target environments there were challenges in picking the right version of package.
• Since packages are not precompiled the application load time becomes slow

To overcome these issues Asp.net core 2.0 has introduced the concept of runtime store using which you can package and deploy applications against a known set of packages that already exist in target environments.

Continue reading →

Step 1:

Download and install .net core sdk from

https://www.microsoft.com/net/download/core

if you already have Visual studio installed you can install “Visual Studio 2017 Tools” else install “Windows (x64) Installer” if you want to work from command line only

Step 2:

When setup finishes it will install all required tools and also setup the path variable so that all CLI tools are available via command line

Continue reading →

As you might already be aware Asp.net core is a platform made of nuget packages. There are different packages targeting different version of frameworks available say .net 4.6, Asp.net core 1.0,1.1 and 2.0. We generally classify frameworks into 2 categories:

• Traditional framework e.g. .net 4.6 which includes .Net framework where most of things are predefined and need not be configured
• Package-based frameworks which are created entirely from scratch by choosing packages as and when required

Package based frameworks are not easy to use and required a different/higher level of understanding of all required packages and most of the .net developers are used to work with predefined templates provided by visual studio.

This problem has been work around by introducing the concept of metapackages which are a collection of commonly used packages required by apps.

In older versions of .net core tools (both project.json and csproj-based tools) by default specified both a framework and a metapackage but in later versions metapackages were tied to specific frameworks . Depending on targeted framework appropriate metapackage is already added to project. This feature is also called as implicit referencing of metapackages. For example

Continue reading →

Razor pages support has been added to asp.net core MVC which makes coding page-focused scenarios easier and more productive. Razor page support is enabled in Startup.cs file as

public class Startup
{
    public void ConfigureServices(IServiceCollection services)
    {
        // Includes this line to support for Razor Pages and controllers.
        services.AddMvc();
    }

    public void Configure(IApplicationBuilder app)
    {
        app.UseMvc();
    }
}

Continue reading →

Microsoft recently announced Asp.net version 2.0 with lot of new and exciting features and enhancement. This update comes on top of the first version i.e. Asp.net Core 1.0 also known as Asp.net 5.0.  To install Asp.net core 2.0 update:

Install Visual Studio 15.3 or later with the following workloads:

• ASP.NET and web development
• .NET Core cross-platform development

Various new features that have been shipped with asp.net core 2.0

• Razor Pages Support
• NET Core metapackage
• .NET Standard 2.0
• Runtime Store
• Configuration update
• Logging Update
• Authentication update
• Identity Update
• Kestrel improvements
• WebListener renamed to HttpSys
• Hosting startup and Application Insights
• Automatic use of anti-forgery tokens
• Automatic precompilation
• Razor support for C# 7.1

Continue reading →