aspnetcore

Commit Graph

Author	SHA1	Message	Date
Doug Bunting	0ae7fd0a93	Remove project name from output path - aspnet/Coherence-Signed#187 - remove `<RootNamespace>` settings but maintain other unique aspects e.g. `<DnxInvisibleContent ... />` - in a few cases, standardize on VS version `14.0` and not something more specific	2016-03-02 16:39:31 -08:00
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

Author

SHA1

Message

Date

Doug Bunting

0ae7fd0a93

Remove project name from output path

- aspnet/Coherence-Signed#187
- remove `<RootNamespace>` settings but maintain other unique aspects e.g. `<DnxInvisibleContent ... />`
- in a few cases, standardize on VS version `14.0` and not something more specific

2016-03-02 16:39:31 -08:00

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

2 Commits