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
105d3353cf
🔥 Remove migrations end point
2015-03-23 15:56:30 -07:00
b66b2df264
React to hosting
2015-03-19 11:22:22 -07:00
616ccb514f
Missed update to use builder in one place
2015-03-11 13:55:31 -07:00
b016764f26
Went a bit too far. :-)
2015-03-11 13:47:33 -07:00
f4c05c8b09
Update to use DbContextOptionsBuilder
2015-03-11 13:15:22 -07:00
a65ebbf1f1
React to EF change
2015-02-26 15:31:49 -08:00
66252ff736
React to EF namespace change
2015-02-13 14:56:28 -08:00
a09d8a4ead
React to Migrations changes
2015-02-10 11:07:18 -08:00
4139f3f18b
React to EF changes in tests.
2015-02-05 11:09:32 -08:00
32e28a8fc8
Reacting to API changes in EntityFramework Migrations
2015-01-07 14:51:05 -08:00
f76583b18b
Reacting to API changes in EntityFramework
2014-12-19 10:47:45 -08:00
e6fdb8cbd2
React to EF dynamic services changes
2014-11-25 13:38:22 -08:00
6f8407bca4
Reacting to EF change
2014-11-21 11:42:38 -08:00
ef544d9baa
Update Microsoft.AspNet.Diagnostics.Entity to build in this repo
...
Previous commit copied code verbatim from EF repo
This commit updates it to build in this repo
2014-11-18 15:12:13 -08:00
fad5ba4323
Copy of Microsoft.AspNet.Diagnostics.Entity code from EntityFramework
...
Straight copy of code with no modification so that we have a baseline of changes made to port the code to the Diagnostics repo
2014-11-17 15:49:09 -08:00
Rowan Miller
Hao Kung
ajcvickers
Brice Lambson
mikary