Search code examples
c#.netlinq-to-sqlmdfdata-persistence

C# 2 versions of same MDF file

I have MDF file which i use as DB and connecting to it using Linq-to-SQL.

my connection string is: 

<add name="TasteTeam.Properties.Settings.TasteDBConnectionString" connectionString="Data Source=(LocalDB)\v11.0; AttachDbFilename=|DataDirectory|\TasteDB.mdf;Integrated Security=True" providerName="System.Data.SqlClient" />

my problem is that when i run the program and adds data to a table it adds into the MDF file that in the bin folder instead of the main MDF file.

this situation causes the MDF file to be empty every time i restart myprogram instead of persisting the data.

what can i do to make both MDF and the tmp MDF file in the bin be the same file (i already tried all the "copy to output directory" options but nothing seem to help)

Solution

  • The whole AttachDbFileName= approach is flawed - at best! When running your app in Visual Studio, it will be copying around the .mdf file (from your App_Data directory to the output directory - typically .\bin\debug - where you app runs) and most likely, your INSERT works just fine - but you're just looking at the wrong .mdf file in the end!

    If you want to stick with this approach, then try putting a breakpoint on the myConnection.Close() call - and then inspect the .mdf file with SQL Server Mgmt Studio Express - I'm almost certain your data is there.

    The real solution in my opinion would be to

    1. install SQL Server Express (and you've already done that anyway)

    2. install SQL Server Management Studio Express

    3. create your database in SSMS Express, give it a logical name (e.g. TasteDB)

    4. connect to it using its logical database name (given when you create it on the server) - and don't mess around with physical database files and user instances. In that case, your connection string would be something like:

      Data Source=.\\SQLEXPRESS;Database=TasteDB;Integrated Security=True

      and everything else is exactly the same as before...

    Also see Aaron Bertrand's excellent blog post Bad habits to kick: using AttachDbFileName for more background info.