aspnetcore/test/Microsoft.AspNet.Diagnostic...
Rowan Miller 1c26436041 Bring back "Apply Migrations" button on database error page
Mostly just a revert of the commit that removed this functionality, with a few changes:
* Perform proper JavaScript encoding in the script part of the database error page Views/BaseView.cs
* Use the builder pattern in the UseXyz extension methods on IApplicationBuilder (per #184). Also applying this to DatabaseErrorPageOptions to keep things consistent.
* Fixing a few tests that were getting the context from DI but putting it in a using block so that it got disposed (rather than letting DI handle disposing).
2015-10-20 09:29:15 -07:00
..
Helpers Update LICENSE.txt and license header on files. 2015-05-01 13:46:24 -07:00
ApiConsistencyTest.cs Update LICENSE.txt and license header on files. 2015-05-01 13:46:24 -07:00
ApiConsistencyTestBase.cs Update LICENSE.txt and license header on files. 2015-05-01 13:46:24 -07:00
DatabaseErrorPageOptionsTest.cs Bring back "Apply Migrations" button on database error page 2015-10-20 09:29:15 -07:00
DatabaseErrorPageTest.cs Bring back "Apply Migrations" button on database error page 2015-10-20 09:29:15 -07:00
Microsoft.AspNet.Diagnostics.Entity.Tests.xproj
TestHelperExtensions.cs Renaming Microsoft.Framework.* -> Microsoft.Extensions.* 2015-10-03 15:44:46 -07:00
project.json Revert "React to aspnet/EntityFramework#2613" 2015-07-21 15:35:20 -07:00