Consider adding UseKestrel extension method to IWebHostBuilder

[davidfowl]

A comment from @NickCraver here aspnet/IISIntegration#105 (comment). It would be nice if we started to follow this pattern. It would allow servers to expose strongly typed extension methods (similar to our middleware pattern).

[davidfowl]

/cc @DamianEdwards @Tratcher @halter73 @lodejard

[ArieJones]

+1 on this as it does feel very unnatural passing a string to .UseServer()

[Tratcher]

Do it.

Should there also be an overload that takes some ketrel Options / configureOptions and registers them in DI so they can be injected into the ServerFactory? Most of IKestrelServerInformation would qualify.

[davidfowl]

@Tratcher I was thinking about that as well. It would be a cleaner way to configure the server settings.

var host = new WebHostBuilder()
    .UseKestrel()
    .UseStartup<StartupHelloWorld>()
    .Build();

host.Run();

You could also configure the server outside of the application making it more portable. It wouldn't take away from configuring things in startup of course but it is cleaner.

var host = new WebHostBuilder()
    .UseKestrel(options =>
     {
         options.NoDelay = true;
         options.ThreadCount = 4;
         options.UseHttps(...);
     })
    .UseStartup<StartupHelloWorld>()
    .Build();

host.Run();

[davidfowl]

/cc @muratg @Eilon

[smbecker]

Isn't options.UseKestrelHttps redundant since you are inside the UseKestrel configure block?

[davidfowl]

@smbecker Fixed

[Eilon]

Looks nice to me.

[davidfowl]

We should also remove these as a result of this:

https://github.com/aspnet/KestrelHttpServer/blob/dev/src/Microsoft.AspNetCore.Server.Kestrel.Https/HttpsApplicationBuilderExtensions.cs

It clears up the fact that these aren't actually pieces of middleware but server configuration.

[muratg]

Putting it optimistically in RC2.