Consider making 1EF use the ASP.NET connection if present


It can be confusing when ASP.NET adds a "Default Connection" to the config file but then EF doesn't use this connection. In the 1EF tooling we should consider making the two play nicer together, possibly be detecting if there is such a connection string and then scaffolding EF to use it.


kjopc wrote Sep 15, 2013 at 2:15 AM

It's annoying to require multiple connection strings in the web.config just because EF has adopted its own format. Could you guys get it together?

RoMiller wrote Dec 12, 2013 at 10:15 PM

EF Team Triage: Moving issues with Impact set to Low out of the 6.1.0 release as we only have time to address High and Medium issues in this release. We will re-triage these issues for future releases.

This does not exclude someone outside of the Microsoft EF team from contributing the change/fix in 6.1.0.