This is a similar piece to another post of mine from a few years ago Run a Windows Azure cloud service locally without the Azure compute emulator
So you’re working on a Service Fabric application which has an ASP.NET Web api host project. I find the debugging experience painful, for two reasons:
- Time to start debugging the project is a minimum of 45 seconds, every time, because the app gets deployed to a local service fabric cluster which takes forever.
- You need to remember to run Visual Studio as administrator in order for the above local deployment to succeed.
If either of these things bug you, then here’s a possible solution. Once we’re done you’ll be able to set the Web project in your solution as the StartUp project instead of the Service Fabric application, for much faster debugging, and you’ll no longer need to run VS as admin.
First, change the Program.cs in the Web project:
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("Web1Type",
context => new WebHost(context)).GetAwaiter().GetResult();
ServiceEventSource.Current.ServiceTypeRegistered(Process.GetCurrentProcess().Id, typeof(Web1).Name);
// Prevents this host process from terminating so services keeps running.
Thread.Sleep(Timeout.Infinite);
}
catch (Exception e)
{
ServiceEventSource.Current.ServiceHostInitializationFailed(e.ToString());
throw;
}
}
If the ASPNETCORE_ENVIRONMENT setting is Development, then it won’t use Service Fabric at all and will just use a plain ol’ ASP.NET Core WebHostBuilder to start the web host.
You’ll also need to change your Debug target to be the Web project, instead of IISExpress, via the VS Standard toolbar.
And just like that the app startup time has shrunk from around 40 seconds to around 5 seconds. Or from an unbearable 100 seconds for the application the team I just joined is working on.
Matt's work blog 