1

I had developed a WPF application, and its backend is a SQL Server CE .SDF file. In setup and deployment project I added .SDF file in it

The issue is: to access and get records from the .SDF file we require an additional software. Please find the below Link

https://www.microsoft.com/en-in/download/details.aspx?id=17876

It has 2 exe files

  1. 64 Bit
  2. 86/32 Bit

Visual Studio directly installs this software when we install VS

On a client system, I didn't find these files so I am unable to access the .SDF file and get records from it

I need to Copy these files in Application folder and Automatically Install it if the above software is not Present in the PC

Now I am Manually Installing these software(exe ) in Each PC

marc_s
  • 732,580
  • 175
  • 1,330
  • 1,459
Rajesh Akshith
  • 301
  • 3
  • 14
  • 1
    Very unclear - what **exactly** do you mean by *SQL Server Compact DB exe file* ?? SQL Server Compact is just a handful of DLL's that you package with your application, and a `.sdf` file that you package or create - there's no external `.exe` of any sort needed to work with a SQL Server CE database file ..... – marc_s Apr 25 '16 at 06:25
  • Marcs Please check my Question I had Updated the Question – Rajesh Akshith Apr 25 '16 at 06:39
  • Again: ***NO*** you don't need any additional EXE based software! You need to simply **ship** the relevant SQL Server Compact DLL's along with your software, **and that's it!** No additional software, no additional install needed! – marc_s Apr 25 '16 at 07:38

1 Answers1

3

You're mistaken - to deploy a SQL Server CE 4.0 based application, you do NOT need to deploy and/or install any additional software to your client system - it suffices to include the necessary, relevant SQL Server CE 4.0 DLL's into your application (into the bin or lib folder or something), and just ship those files with your application. That's all you need - no server-side or client-side install needed ! (That's the WHOLE POINT of using SQL Server CE, after all!)

See these links for in-depth descriptions of how to do it:

Right here on Stackoverflow:

Another way to do it:

Official MSDN documentation:

Community
  • 1
  • 1
marc_s
  • 732,580
  • 175
  • 1,330
  • 1,459