I've been reading about how wonderful Visual Studio 2013's new Sql Server Data Tools are, and about the new localdb database server, etc., so I've been trying to do what would seem to me to be the point of the whole thing - to embed a local test/development database in a VS solution, so that when I check out a project into a clean directory, on a new machine, I can just run my application, connected to the database in the solution.

But I've not been able to figure out how to do it.

Can anyone give me any hints? Or directions to a tutorial?

*Adding some clarification*

There's a tutorial on how to include a localdb database in a project, on MSDN, here:

[Local Data Overview](http://msdn.microsoft.com/en-us/library/ms233817.aspx)

But, unfortunately, it doesn't work. I followed through the instructions, exactly, and it all seemed to work, until I moved the solution folder to a new location, at which point it lost track of the database.

The problem is the connection string, which contains an absolute path to where the database was when it was created. Which is useless. I need to be able to check out a project to any location, on any machine, and have it build and run there.

```
<connectionStrings>
    <add name="ConnectLocalData.Properties.Settings.SampleDatabaseConnectionString"
        connectionString="Data Source=(LocalDB)\v11.0;AttachDbFilename=E:\dev\Experiments\LocalDbWalkthrough\SampleDatabaseWalkthrough\SampleDatabase.mdf;Integrated Security=True;Connect Timeout=30"
        providerName="System.Data.SqlClient"
    />
</connectionStrings>

```

Apparently, this question has been asked before: 

[Make the connectionstring's AttachDbFilename relative in config file](https://stackoverflow.com/questions/24008830/make-the-connectionstrings-attachdbfilename-relative-in-config-file)

But that question has no answers.