Go to file

Rowan Miller 111dab7ddf 🐛 No database error page for existing databases When there is an existing database and no migrations are present, then we should just display the standard error page as they are not using migrations and need to adjust their mapping code to match the existing schema. Resolve #182		2015-10-20 09:23:42 -07:00
samples	Renaming Microsoft.Framework.* -> Microsoft.Extensions.*	2015-10-03 15:44:46 -07:00
src	🐛 No database error page for existing databases	2015-10-20 09:23:42 -07:00
test	🐛 No database error page for existing databases	2015-10-20 09:23:42 -07:00
.gitattributes	…
.gitignore	…
.travis.yml	…
CONTRIBUTING.md	…
DiagnosticsPages.sln	…
LICENSE.txt	…
NuGet.config	Update nuget.exe and corresponding feeds to v3.	2015-09-17 18:33:07 -07:00
NuGetPackageVerifier.json	Enabling NuGetPackageVerifier	2015-09-22 16:00:47 -07:00
README.md	…
appveyor.yml	…
build.cmd	Fix local build break	2015-10-12 12:51:39 -07:00
build.sh	React to aspnet/Universe#290 fix	2015-10-10 19:53:14 -07:00
global.json	…
makefile.shade	* Fix PageGenerator	2015-10-16 10:44:55 -07:00

README.md

ASP.NET DiagnosticsPages

AppVeyor:

Travis:

Diagnostics middleware.

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