How to run ASP.Net core MVC solution locally without deploying to Service Fabric Cluster

If you are working on ASP.net web application which is hosted in a Service Fabric Cluster, you might have come across the pain in debugging these application. Luckily there is an alternative to avoid the hassle in setting up service fabric development environment in the local machine. Below changes to your code in Program.cs file will help you debug your ASP.Net web application locally.

Program.cs file in ASP.net web application

using System; using System.Diagnostics; using System.IO; using System.Threading; using Microsoft.AspNetCore.Hosting; using Microsoft.ServiceFabric.Services.Runtime; namespace HelloWorld { internal static class Program { private static void Main() { if (UseServiceFabric()) { StartServiceFabric(); } else { StartWebHost(); } } private static bool UseServiceFabric() { var webHostBuilder = new WebHostBuilder(); var environment = webHostBuilder.GetSetting("environment"); return environment != "Development"; } private static void StartWebHost() { var builder = new WebHostBuilder() .UseKestrel() .UseContentRoot(Directory.GetCurrentDirectory()) .UseStartup<Startup>(); var host = builder.Build(); host.Run(); } private static void StartServiceFabric() { try { // The ServiceManifest.XML file defines one or more service type names. // Registering a service maps a service type name to a .NET type. // When Service Fabric creates an instance of this service type, // an instance of the class is created in this host process. ServiceRuntime.RegisterServiceAsync("WebApplicationName", context => new Configuration(context)).GetAwaiter().GetResult(); ServiceEventSource.Current.ServiceTypeRegistered(Process.GetCurrentProcess().Id, typeof(Configuration).Name); // Prevents this host process from terminating so services keeps running. Thread.Sleep(Timeout.Infinite); } catch (Exception ex) { ServiceEventSource.Current.ServiceHostInitializationFailed(ex.ToString()); throw ex; } } } }