Breaking Changes to LocalDB: Applies to SQL 2014; take a look over this article and try to use (localdb)\mssqllocaldb
as server name to connect to the LocalDB automatic instance, for example:
<connectionStrings>
<add name="ProductsContext" connectionString="Data Source=(localdb)\mssqllocaldb;
...
The article also mentions the use of 2012 SSMS to connect to the 2014 LocalDB. Which leads me to believe that you might have multiple versions of SQL installed – which leads me to point out this SO answer that suggests changing the default name of your LocalDB “instance” to avoid other version mismatch issues that might arise going forward; mentioned not as source of issue, but to raise awareness of potential clashes that multiple SQL version installed on a single dev machine might lead to … and something to get in the habit of in order to avoid some.
Another thing worth mentioning – if you’ve gotten your instance in an unusable state due to tinkering with it to try and fix this problem, then it might be worth starting over – uninstall, reinstall – then try using the mssqllocaldb
value instead of v12.0
and see if that corrects your issue.