best tutorial ASP.NET Core 1.0 Project |

CheapASPNETHostingReview.com | Best and cheap ASP.NET Hosting. Some times after hosting web application on the server, we get unexpected error as shown in the below fig. But we did get the detailed message for the unexpected errror. In this article, I would like to share how can we get detailed message for the unexpected error.

This type of unexpected error may occurs on local or remote server. In asp.net, we can find the exact error message by setting mode=”Off” with in customErrors tag in web.config of our application. This is the way by which we can find out the exact error in our web application

 &lt;system.web&gt; 
&lt;customErrors mode="Off"&gt;
 &lt;/customErrors&gt; 
 ...
 ...
 &lt;/system.web&gt;

<system.web>

</customErrors>

...

</system.web>

When we set the customErrors mode=”Off” then we can easily track the error in the application as shown in the fig.

In Asp.net, there are three error modes to trace an error. These modes decide whether or not an error message is displayed. RemoteOnly mode is default mode for displaying error messages.

Off Mode
This mode is responsible for displaying error mesage on local and remote server in case of an error.
On Mode
This mode is responsible for displaying custom error page with message on local and remote server in case of an error. By using this mode, we can show our own custom error messages page for specific errors on local and remote server.
RemoteOnly
This mode is responsible for displaying error mesage on remote server only in case of an error. By using this mode, we can show our own custom error messages page for specific errors on remote server only.

I hope you will enjoy these tricks while programming with Asp.Net. I would like to have feedback from my blog readers. Your valuable feedback, question, or comments about this article are always welcome.

CheapASPNETHostingReview.com | Best and cheap ASP.NET Core 1.0 hosting. According to tutorialspoint website about the configuration related to ASP.NET Core project. In Solution Explorer, you will see the Startup.cs file. If you have worked with previous versions of ASP.NET Core, you will probably expect to see a global.asax file, which was one place where you could write codes to execute during startup of a web application.

You would also expect to see a web.config file containing all the configuration parameters your application needed to execute.
In ASP.NET Core those files are all gone, and instead of configuration and startup code are loaded from Startup.cs.
There is a Startup class inside the file and in this class you can configure your application and even configure your configuration sources.

Here is the default implementation in the Startup.cs file.

using System;
using System.Collections.Generic;
using System.Linq;
using System.Threading.Tasks;

using Microsoft.AspNetCore.Builder;
using Microsoft.AspNetCore.Hosting;
using Microsoft.AspNetCore.Http;

using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Logging; 

namespace FirstAppDemo {
   public class Startup {
      // This method gets called by the runtime.
      // Use this method to add services to the container.
      // For more information on how to configure your application,
      // visit http://go.microsoft.com/fwlink/?LinkID=398940
      public void ConfigureServices(IServiceCollection services) {
      } 
     
      // This method gets called by the runtime. Use this method to configure
      // the HTTP request pipeline.
      public void Configure(IApplicationBuilder app, IHostingEnvironment env,
         ILoggerFactory loggerFactory) {
         loggerFactory.AddConsole(); 
        
         if (env.IsDevelopment()) {
            app.UseDeveloperExceptionPage();
         } 
         app.Run(async (context) =&gt; {
            await context.Response.WriteAsync("Hello World!");
         });
      }
   }
}

using System;

using System.Collections.Generic;

using System.Linq;

using System.Threading.Tasks;

using Microsoft.AspNetCore.Builder;

using Microsoft.AspNetCore.Hosting;

using Microsoft.AspNetCore.Http;

using Microsoft.Extensions.DependencyInjection;

using Microsoft.Extensions.Logging;

namespace FirstAppDemo {

public class Startup {

// This method gets called by the runtime.

// Use this method to add services to the container.

// For more information on how to configure your application,

// visit http://go.microsoft.com/fwlink/?LinkID=398940

public void ConfigureServices(IServiceCollection services) {

}

// This method gets called by the runtime. Use this method to configure

// the HTTP request pipeline.

public void Configure(IApplicationBuilder app, IHostingEnvironment env,

ILoggerFactory loggerFactory) {

loggerFactory.AddConsole();

if (env.IsDevelopment()) {

app.UseDeveloperExceptionPage();

}

app.Run(async (context) => {

await context.Response.WriteAsync("Hello World!");

});

}

In the Startup class, there are two methods where most of our work will take place. The Configure method of the class is where you build your HTTP processing pipeline.

This defines how your application responds to requests. Currently this application can only say Hello World! and if we want the application to behave differently, we will need to change the pipeline around by adding additional code in this Configure method.
For example, if we want to serve the static files such as an index.html file, we will need to add some code to the Configure method.
You can also have an error page or route requests to an ASP.NET MVC controller; both of these scenarios will also require to do some work in this Configure method.
In the Startup class, you will also see the ConfigureServices() method. This helps you configure components for your application.

Right now, we have a hard-coded string for every response — the Hello World! string. Instead of hard-coding the string, we want to load this string from some component that knows the text that we want to display.

This other component might load that text from a database or a web service or a JSON file, it doesn’t matter where exactly it is.
We will just set up a scenario so that we do not have this hard-coded string.

In the Solution Explorer, right-click on your project node and select Add → New Item

In the left pane, select Installed → Code and then in the middle pane, select the JSON File. Call this file AppSettings.json and click on the Add button as in the above screenshot.

We can also have our program read the text from the file instead of having the Hello World! String in Startup.cs. Let us add the following code in AppSettings.json file.

{
   "message": "Hello, World! this message is from configuration file..."
}

{

"message": "Hello, World! this message is from configuration file..."

}

Now we need to access this message from the Startup.cs file. Here is the implementation of the Startup.cs file which will read the above message from the JSON file.

using Microsoft.AspNet.Builder;
using Microsoft.AspNet.Hosting;
using Microsoft.AspNet.Http;

using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Configuration; 

namespace FirstAppDemo {
   public class Startup {
      public Startup() {
         var builder = new ConfigurationBuilder()  
            .AddJsonFile("AppSettings.json");
         Configuration = builder.Build();
      } 
      public IConfiguration Configuration { get; set; } 
     
      // This method gets called by the runtime.
      // Use this method to add services to the container.
      // For more information on how to configure your application,
      // visit http://go.microsoft.com/fwlink/?LinkID=398940
      public void ConfigureServices(IServiceCollection services) {
      } 
     
      // This method gets called by the runtime. 
      // Use this method to configure the HTTP request pipeline.
      public void Configure(IApplicationBuilder app) {
         app.UseIISPlatformHandler(); 
         app.Run(async (context) =&gt; {
            var msg = Configuration["message"];
            await context.Response.WriteAsync(msg);
         }); 
      } 
       
      // Entry point for the application.
      public static void Main(string[] args) =7gt; WebApplication.Run&lt;Startup&gt;(args);
   }
}

using Microsoft.AspNet.Builder;

using Microsoft.AspNet.Hosting;

using Microsoft.AspNet.Http;

using Microsoft.Extensions.DependencyInjection;

using Microsoft.Extensions.Configuration;

namespace FirstAppDemo {

public class Startup {

public Startup() {

var builder = new ConfigurationBuilder()

.AddJsonFile("AppSettings.json");

Configuration = builder.Build();

}

public IConfiguration Configuration { get; set; }

// This method gets called by the runtime.

// Use this method to add services to the container.

// For more information on how to configure your application,

// visit http://go.microsoft.com/fwlink/?LinkID=398940

public void ConfigureServices(IServiceCollection services) {

}

// This method gets called by the runtime.

// Use this method to configure the HTTP request pipeline.

public void Configure(IApplicationBuilder app) {

app.UseIISPlatformHandler();

app.Run(async (context) => {

var msg = Configuration["message"];

await context.Response.WriteAsync(msg);

});

}

// Entry point for the application.

public static void Main(string[] args) =7gt; WebApplication.Run<Startup>(args);

}

Let us now run the application. Once you run the application, it will produce the following output.

I hope this article helpful for you. Happy coding 🙂

best tutorial ASP.NET Core 1.0 Project

How to Turn off Asp.net Custom Errors in Web.config

Off Mode

On Mode

RemoteOnly

Configuration ASP.NET Core 1.0 Project