The Data Source value in the connection string specifies an instance of SQL Server that is not installed. To resolve this issue, you can either choose to install the matching instance of SQL Server or modify the Data Source value in the connection string.
Visual Studio 2013 Database connection and 2017 connection seem to be running the same Microsoft SQL Connection Client, What’s the compatibility differences and how do I Fix this?
Data Source: Microsoft SQL Server Database File (SqlClient)
New Connection String: C:UsersShawnsourcereposServerdatabaseClientRegit.mdf
Old connection String: Data Source=(LocalDB)v11.0;AttachDbFilename=”C:Userssrhea_000DocumentsVisual Studio 2013ProjectsServerdatabaseClientRegit.mdf”;Integrated Security=True;Connect Timeout=30
These are the two instances of SQL that currently showing on my computer, I currently tried modifying the connection to Microsoft SQL Server as it was on VS2013 but as you can see in the connection string its was using V11.0 and 2017 has V13.0.4001 so I thought the database file would automatically upgrade for the new version of the instances SQL in VS2017, by attaching it when modifying the connection type