System.Data.SqlServerCe.dll SQL Server CE 3.5 reference missing after generating .exe file using InstallShield Limited Edition Project

I am using VS 2013 with InstallShield Limited Edition Project.

Everything is working fine in development environment where I have created reference to System.Data.SqlServerCe.dll

After I generate .exe file and install my application it is unable to find reference for SQL Server CE 3.5 thus automatically gets reference for SQL Server CE 4.0 and gave an error.

Incompatible Database Version. If this was a compatible file, run repair. For other cases refer to documentation. [ Db version = 4000000,Requested version = 3505053,File name = /?/C:/Users/someuser/AppData/Local/testapp/testdb.sdf ]

I have tried going through “this” article on MSDN but I can’t find any publish tab in properties of my project.

Furthermore I am deploying System.Data.SqlServerCe.dll and all 7 32bit version SQL Server CE 3.5 dlls with my setup.


Generating single exe InstallShield 2012 limited edtion in visual Studio 2012

I’m using InstallShield Wizard spring limited edition in Visual Studio 2012. I want to know how can I generate a SINGLE .EXE installer file in installshield, I’m now getting two ini files, a cab file,

How can InstallShield check if SQL Server 2005 (3.1) Compact Edition (CE) is installed

I am developing a Windows desktop application which requires the SQL Server 2005 Compact Edition (SQLServerCE31-EN.msi) to be installed. I am using InstallShield 2011 to install this as a pre-requisit

SQL Server CE missing as required prerequisite in InstallShield LE (Visual Studio 2010)

I’ve just enabled InstallShield LE within Visual Studio 2010 and am putting together a setup project. I would like to specify SQL Server CE 4.0 as a required prerequisite such that InstallShield will

setting file permissions with installshield limited edition

The installshield LE has deprecated features. Setting file permssions has been disabled. Is there a way to set file permssions. I tried running a post installation exe which uses icacls to set permiss

Open .ISM with InstallShield Limited Edition

Environment: TFS 2010 + VisualStudio 2010 + InstallShield Limited Edition. I am sorry to be novice about InstallShield. I have a InstallShield project with .ISM extension. Is it possible to load it i

Forcing Installshield to install SQL Server CE before it will install main application

Any clue how to force Installshield to install SQL Server CE before it will install the main application? (SQL Server CE is included in the installation project) Thanks!

Installshield Limited Edition licencing on build server

I have recently installed Installshield LE on my local PC for vs2010, built a package and now wanting it to be built on our build server. I have also installed it on our build server. I am getting the

Run solution exe after installation using installshield

I want to run my exe after installation using InstallShield. InstallShield setup install successfull but not run the exe. I found anouther way to add exe in startup but it runs after restart. As per I

Multi-Instance MSI with InstallShield 2012 Limited Edition

I’ve created a .msi of my product using InstallShield 2012 Limited Edition project via Visual Studio 2012. It works fine when installing a single instance of it. But when trying to install another, th

Using InstallShield Limited Edition, how do I remove the uninstall dialog that requires a reboot

I am creating an installer for a web application and using InstallShield Limited Edition. I can install just fine, but when I run the ‘uninstall’, I get a dialog box that says that a reboot is require


No, the issue is that your database file is in 4.0 format. As you can see from the error message, the engine is trying to open a 3,5 file, but gets a 4,0 file instead. So your application is using the 3,5 engine.

The problem was when I was trying to deploy msi package using InstallShield it used different build setting(x64) than my current setting(x86) which was causing my application to get the reference of x64 Sql Server CE 4.0 files. So it was fixed by changing setting of singleimage compiling option.