.Net Framework support about beatpulse

[eiximenis]

Hi @rogerbramon

I think this should be doable because we are using netstandard. Which:

• versions of netfx are expected to be supported?
• asp.net frameworks? MVC? WebApi? Webforms?

[rogerbramon]

Hi @eiximenis

We're currently targeting 4.5.2 but we should be able to easily upgrade to 4.6.1 or 4.7. Regarding frameworks most of them are using WebApi and a couple are using MVC.

I guess that the way BeatPulse is registered should be changed anyway because it's very coupled with .Net Core pipeline. Besides that, there are other parts, such as the IBeatPulseLiveness, that also depend on aspnet core apis (Microsoft.AspNetCore.Http in this case). So, as it is implemented right now the different Liveness libraries could not be used neither. Is that right?

Thanks!

[unaizorrilla]

At this moment, BeatPulse is "Liveness, health check library for ASP.NET Core Applications". The team is working on a refactoring (for vnext) to support different host ( ASP.NET Core and Generic Host ) and plattforms ( ASP.NET Core / ASP.NET ), but next version is not planned to be release soon.

[hasansachdev]

what would be the .net framework equivalent of this?

public static IWebHost BuildWebHost(string[] args) =>
        WebHost.CreateDefaultBuilder(args)
               .UseBeatPulse(options=>
                {
                   options.ConfigurePath(path:"health") //default hc
                        .ConfigureTimeout(milliseconds:1500) // default -1 infinitely
                        .ConfigureDetailedOutput(detailedOutput:true,includeExceptionMessages:true); //default (true,false)
                }).UseStartup<Startup>().Build();