Develop Reference

How does my Visual Studio program reference the correct database file?

I have a C# application that creates an installer with a Setup project in Visual Studio. It all works fine except for the SQLite database that I am trying to include.
What I have done:
Added the database file from my solution to the Application Folder of the Setup project.
Stored the connection string in my code where I use it to create the connection.
private const string conString = "DATASOURCE = HCATDatabase.sqlite; VERSION = 3;";
SQLiteConnection dbConnection = new SQLiteConnection(conString);`
Rebuilt the Setup project and the Solution.
Installed the program from the created installation.
What happened when I fired the installed application:
The database gives errors like "No such table", while the database in my solution does have these tables.
The application shows data that is not in the database from my solution.
I compared the database files with DB Browser (the one from my project that I included in my Setup project and the one in the installed program's file) and they are identical.
So somehow the program uses a different (third) database file.
How can I find out where the program gets this file from and how can I change it to use the proper file?
UPDATE: I have found thanks to #Roger Lipscombe that the program uses a database file in C:\Users\User\AppData\Local\VirtualStore\Program Files (x86)\ProgramCompany\MyProgram.
UPDATE 2: I deleted the folders (that were pretty old) in the above directory and that fixed everything, the program now references the correct database. I would love it if someone could explain all of this.

Can't connect to local database after deployment

I am writing a program in Visual C# 2015. I have created a local database from within the IDE and everything seems to work fine after building and running locally. However, after publishing the application and installing on another machine I get an argument exception error at attachdbfilename. I have included the database as a content file. The ClickOnce does copy the database to a folder under APPS in my Appdata folder. I have installed SQL Local DB edition on the target machine. The database name is ConnectionsDatabase.mdf.
These are definitions in my Settings.Designer.cs file.
[global::System.Configuration.SpecialSettingAttribute(global::System.Configuration.SpecialSetting.ConnectionString)]
[global::System.Configuration.DefaultSettingValueAttribute("Data Source=(LocalDB)\\MSSQLLocalDB;AttachDbFilename=|DataDirectory|\\ConnectionSet" +
"tings.mdf;Integrated Security=True; User Instance=True")]
[global::System.Configuration.DefaultSettingValueAttribute("Data Source=(LocalDB)\\MSSQLLocalDB;AttachDbFilename=|DataDirectory|\\ConnectionsDa" +
"tabase.mdf;Integrated Security=True; User Instance=True")]
Not sure if they should both be there for just 1 database.
This is what I use for connection string within the appropriate classes.
using
(SqlConnection con = new SqlConnection(Store_Switcher.Properties.Settings.Default.ConnectionsDatabaseConnectionString))
I am willing to share any and all project files that are needed. Keep in mind this is a small application that will be installed on several different machines. Please help!! This is driving me crazy!

AttachDbFilename=|DataDirectory|\ConnectionSet" + "tings.mdf
should be
AttachDbFilename=|DataDirectory|\ConnectionData" + "base.mdf
in your designer file. or vice versa. you have a disconnect in file names.
EDIT:
You mean "invalid value for key"? The problem sounds like whatever path you are using for the database on the target system doesn't match your development machine.
You even say "The ClickOnce does copy the database to a folder under APPS in my Appdata folder. " So maybe on your dev box you have c:\myapp\App_Data\ConnectionData.mdf and on target it is c:\myapp\App_data\APPS\ConnectionData.mdf after it gets deployed.This won't work. Get rid of the APPS, or change your code so the deployment folder is the same as on your dev box. This is a path issue.

Unable to update database .MDF is Read Only

I have a local DB that I have in an application. When I install it on another machine I get the error
Unable to update database.. .mdf is read only.
I was able to get around it by editing my permissions on the .mdf and log file themselves. I did some research and noticed that I may want to install the database to a shared folder. However, I am not sure how to do that and the answers I did come across did not make a whole lot of sense to be.
//My connection string
SqlConnection con = new SqlConnection(#"Data Source=(LocalDB)\v11.0;AttachDbFilename=|DataDirectory|AssetDatabase.mdf;Integrated Security=True");
Any guidance would be greatly appreciated. I am learning.

Just go to the program files and find the folder of the installed program.
Just right click the .mdf file in the folder and click PROPERTIES.
In PROPERTIES TAB -> SECURITY -> you'll see Group or Usernames.
In that select the User to which u want to give Access to the file.
If for that user the PERMISSION is not set to FULL CONTROL.
TO CHANGE PERMISSIONS -> CLICK EDIT.
Now the Group or Username box will open.
In that Select The User -> Select FULL CONTROL in Permission Box.
Now follow the steps for the log file too. IF Needed.
OR
Just install your application in different folder other than ProgramFile(x86)

The MDF file would be readonly either because the readonly file attribute flag is set, in which case you have to unset it, or another program has the MDF file locked as readonly. Are you running a version of SQL server that is using that file?
I've never seen a connection to the MDF file directly, usually it's done via the server, and the server will manage all the IO for the MDF file.
E.g. a typical connection string for SQL Server:
Database=<dbname>;Server=<servername>;MultipleActiveResultSets=True;Connection Timeout=10;User Id=<username>;Password=<password>;
Additional links:
1) Failed to update .mdf database because the database is read-only (Windows application)
2) Failed to update database because it is read-only
3) Failed to update database "*.mdf" because read only EntityFramework
4) http://www.codeproject.com/Questions/183758/Failed-to-update-mdf-database-because-the-database

First stop the SQLEXPRESS service from local-Services menu and then try to move and connect the database again by attaching database option in SQLEXPRESS. it should work. it works for me. :)

I solved the same problem as follows:
While creating "Setup", I manually added my database files database.mdf and database_log.ldf into the Application Folder file. But after adding these files, make sure that the ReadOnly option in the Properties section is False.
Also "connectionString" I use:
connectionString="Data Source=(LocalDB)\MSSQLLocalDB;AttachDbFilename=|DataDirectory|\database.mdf;Integrated Security=True;Connect Timeout=30"

just remove the .mdf file location to c:\ or desktop or anywhere but not in
%program file directory

if your database file on the C volume,
try to move the .mfd file to D volume

Automatically install access database when creating setup file in c#

I Have created a c# application which is using access database.
I have deploy the application successfully.
what I want is install the access database automatically in other users computer automatically.
I have tried to change the app.config files connection string and no use..:(
help me

Not sure what you mean, but if your database is part of your solution you can copy it to the output directory:

You have to be more specific. Did you install the application using installer? Copying and pasting?
Maybe these would help:
StackOverflow - "How to install visual studio 2010 setup project with MS Access database on a computer which is not having Office 2010 installed?"
CodeProject - Deploy your Application and Database
MSDN Forums - "How to attach sql database file to creating .exe setup in c#"

Copy the access db to a folder in programdata with the setup. Connect to this db in your code. You don't need a connectionstring in app.config if the user is not allowed to specify the db path.
Environment.GetFolderPath(Environment.SpecialFolder.CommonApplicationData);
Your setup should be able to deploy to a programdata folder.

If you want to create .exe Setup Project of your Dot Net Application which is using MS Access DATA BASES. then simply follow this steps. Please read this one for a moment before to proceed these steps.Connect with MS Access Data Base in Dot net.
When you are going to create the exe file then your data base connection string should be like this(means there should be no directory in #"Data source, Just direct put the name of your data base, because in .exe file when you add your data base file, then it is in the same directory.
System.Data.OleDb.OleDbConnection conn = new System.Data.OleDb.OleDbConnection();
conn.ConnectionString = #"Provider=Microsoft.ACE.OLEDB.12.0;" +
#"Data source=MyDataBase.accdb";
Right click on your solution file. (like in Solution Explorer "Solution 'MyProject' ")
Select Add -->New Project -->Other Project Types
Select "Setup"
A New project will be added named setup (with a new tab added to
editor as File System )
Now right click on application folder -->select add -->select folder
new folder will be added under application folder * Now Right click
on newly added folder -->select add -->select file * Add File dialog
will be popup
Select your Db file (means from a "Browse" Button there go and select your Access Data Base )
Select Setup project and build.. Now your
installer will have your DB.
You can also install it from there.

main considerations while publishing application using SQL server Database

I want to ask about the main considerations we have to put in mind when publishing application using SQLServer database?
I ask this question because I faced a problem when I developed an application using SQL server Database in C# and used it in another machine. The problem is an exception happen in launching the application.
This is the exception message:
<b>"The ConnectionString proberty has not been initialized"</b>. The ConnectionString is in App.config and assing while form loading.
This is the ConnectionString:
<b>"Data Source=.\SQLEXPRESS;Initial Catalog=test;Integrated Security=True;Pooling=False"</b> and it is in this file: appName.exe.config
The application is Desktop application and it's not need for installation just click .exe and it should connect to the existing SQLServer database with the ConncetionString in the appName.exe.config file.

The best way to deploy any type of application will be creating a setup.exe or .msi file.
Since this will ensure the important files which will copy to the target machine. It also provides a well structured file hierarchy along custom action which we can program each and every steps of installation.
It is always good to keep the connection properties in a config file, which helps to change the configuration settings without building the project. The exe will reads data from the config file, so if we changed the values then also it will works fine. While creating the setup project add the configuration settings and deploy or it is also good to have a common setup msi and different config files.
For example the database may be different for servers like DEV,QA,Staging etc. For each sever the msi will be same but the connection string will be different. So there is also a way to create self extracting files which will update the config files . For QA,DEV,Staging etc different self extracting files will be there. by running those files, it is possible to update the server details and authentication details. By providing msi and extracting files, users can install the application very easily