![sql server compact 3.5 sp2 msi files sql server compact 3.5 sp2 msi files](https://xldennis.files.wordpress.com/2010/08/create-ssce-2.png)
- Sql server compact 3.5 sp2 msi files install#
- Sql server compact 3.5 sp2 msi files 64 Bit#
- Sql server compact 3.5 sp2 msi files update#
- Sql server compact 3.5 sp2 msi files Pc#
I also extracted the contents of the installer and could not find any cab files in it either. I looked through the contents of cab files and the files are still from the old version.
Sql server compact 3.5 sp2 msi files update#
I do have SP2 release for Devices installed on my machine which I downloaded from the location above but it did not create or update any cab files.
![sql server compact 3.5 sp2 msi files sql server compact 3.5 sp2 msi files](https://s1.manualzz.com/store/data/007177641_1-6ad8689c0db9a045ab6c602d0a3e35f4-360x466.png)
The version that I believe it should be is I found that the version is still which I believe is the very first release (no service packs) \Program Files\Microsoft SQL Server Compact Edition\v3.5 on my device.
Sql server compact 3.5 sp2 msi files Pc#
I installed the cab anyway and then had a look at the version of the files by copying them over to my PC from It is a simple deployment, of a couple of files and you are in control of what DLL versions your application uses.Thank you for your answer, but I believe that this cab file still contains the old version of the engine. In my opinion this is the only way to go. If you have these all set, then in your installer project all you have to include is the project output of this project and you're good. And the main reference to that you have in your project references should have copy local set to true. They can be added to the project in Visual Studio and then set their project output type to "copy always". If you have SQL Server Compact installed on your machine, they are most likely located at "C:Program FilesMicrosoft SQL Server Compact Editionv3.5". Depending on the features of SQL Server Compact you are using (replication or whatever), there is a handful of DLL files to deploy in your application folder. Including the DLL files in your application folder. The two main ways are:ĭeploying the SQL Server Compact redistributable installer with your project, but this way is painful and also can be unistalled by the end user, or upgraded by Windows updates and breaking your application.
![sql server compact 3.5 sp2 msi files sql server compact 3.5 sp2 msi files](https://www.techyv.com/sites/default/filesx/users/Images/Microsoft-SQL-Server-Compact-3-5-SP2-ENU.jpeg)
There are several ways to deploy an SQL Server Compact project. You don't need it to be in the GAC for SQL Server Compact to run, and it will pick them up from the application directory. Do these need to be installed in the GAC or will locating them in the application directory suffice?
![sql server compact 3.5 sp2 msi files sql server compact 3.5 sp2 msi files](http://lh3.ggpht.com/_S3gOGymJVuE/St8dFyDMYZI/AAAAAAAAAPM/RNM-HLJz_VA/w1200-h630-p-k-no-nu/clip_image002_thumb[2].jpg)
Sql server compact 3.5 sp2 msi files install#
Sql server compact 3.5 sp2 msi files 64 Bit#
I spent a few hours searching for this error already, but all I could find were issues relating to installing on 64 bit Windows and none relating to normal 32 bit that I'm using. When I run the setup.exe (on new Windows XP 32 bit with SP2 and Internet Explorer 7) it installs fine, but when I run the application I get this error: I'm new to SQL Server Compact, so I haven't had to distribute a client database like this before now. I'm using a standard Windows Installer project that creates an MSI file and setup.exe to install the application on a client machine. The client will most likely be 32 bit Windows XP or Windows Vista machines. I'm developing a Windows Forms application using Visual Studio 2008 C# that uses an SQL Server Compact 3.5 database on the client.