Go to file
Ryan Nowak 1afd5b2594 Don't use Map
Fixes aspnet/Diagnostics#511 and aspnet/Diagnostics#514

It's really confusing to people that we use Map. Users expect that the
URL they provide for the health check middleware will only process
exact matches. The way it behaves when using map is not optimal for some
of the common patterns.
2018-10-27 21:01:55 -07:00
.vsts-pipelines/builds
build Add IHealthCheckPublisher for push-based checks (#498) 2018-10-08 17:58:45 -07:00
samples Change 'create' to 'delete' in message 2018-10-21 13:38:59 -07:00
src Don't use Map 2018-10-27 21:01:55 -07:00
test Don't use Map 2018-10-27 21:01:55 -07:00
.appveyor.yml
.gitattributes
.gitignore
.travis.yml
CONTRIBUTING.md Fixed broken link (#504) 2018-10-16 05:04:19 -07:00
DiagnosticsPages.sln Add EFCore DbContext check 2018-10-01 13:33:00 -07:00
Directory.Build.props automated: bulk infrastructure updates. Update bootstrapper scripts and remove unnecessary signing properties 2018-09-28 17:10:32 -07:00
Directory.Build.targets
LICENSE.txt
NuGet.config
NuGetPackageVerifier.json
README.md
build.cmd
build.sh
korebuild-lock.txt Update dependencies.props 2018-09-30 12:10:59 -07:00
korebuild.json
run.cmd
run.ps1 automated: bulk infrastructure updates. Update bootstrapper scripts and remove unnecessary signing properties 2018-09-28 17:10:32 -07:00
run.sh automated: bulk infrastructure updates. Update bootstrapper scripts and remove unnecessary signing properties 2018-09-28 17:10:32 -07:00
version.props Update package branding for 2.2 RTM 2018-10-16 12:48:13 -07:00

README.md

ASP.NET Core Diagnostics

AppVeyor: AppVeyor

Travis: Travis

Diagnostics middleware for reporting info and handling exceptions and errors in ASP.NET Core, and diagnosing Entity Framework Core migrations errors.

This project is part of ASP.NET Core. You can find samples, documentation and getting started instructions for ASP.NET Core at the Home repo.