- #MICROSOFT SQL SERVER COMPACT 3.5 SP2 INSTALL#
- #MICROSOFT SQL SERVER COMPACT 3.5 SP2 UPDATE#
- #MICROSOFT SQL SERVER COMPACT 3.5 SP2 SOFTWARE#
#MICROSOFT SQL SERVER COMPACT 3.5 SP2 INSTALL#
So if I got the point right, it should be enough to take care that the 7 specified dlls plus should be at the applications location? We use not the VS.NET-deployment but a third-party-tool to create our msi-files so it should be enough to ensure that those 7 files plus are available after install process, right? In the meantime, I’ve e-mailed it to you. His response was XML, and it won’t let him put that in there. Well that’s not helpful- why did Kevin Warners last msg lose the info inside his double quotes? I fixed it by setting up the “” section of the app.config file This is the bit you are missing: This is the last dll that you need, and setting copylocal to true means it will include it in the deployment. When I try to install and run it on a machine without SQLCE installed, I get the following error:Īn error occured in the following file – SqlCeFailureĬannot open ‘|DataDirectory|\OpusDb.sdf’. When I run it on my development machine with SQLCE installed, it runs great. I am using a “My.Settings” ConnectionString. All of the files get copied to the output directory as expected. I have my solution setup as you described in this article. I have a vb application using a SQLCE 3.5 sp1 database using Linq with a dbml. There is no SQLCE dll specifically for the EF, so I’m not sure what you’re referencing. NET, so you need to be sure you are targeting the right version of the framework and including it as a prerequisite so your user has it installed. You need to check your connection string. I responded to you via e-mail, and will post some comments here for posterity. I am using the Entity Framework as well, so I have also included the SQLCE dll for that as well.
It doesnt work for me, the build works and publish includes the required files, but when the app runs I get “the specified store provider cannot be found” exception. You can leave a response, or trackback from your own site.Ĥ1 Responses to “How to deploy the SQLServer Compact Edition software locally” You can follow any responses to this entry through the RSS 2.0 feed. This entry was posted on Februat 7:12 pm and is filed under ClickOnce Deployment, Microsoft Technology. This kind of thing tends to annoy customers, which is always a bad thing that can lead to a loss of cash flow, if you know what I mean.įor a easier way to handle updates and let your database change only when you intend it to, you might want to check out my blog entry titled Where do I put my data to keep it safe from ClickOnce updates? I think the title is self-explanatory. If you’re not handling this in your code, it looks like the user has lost his data. In other news about SQLCE databases (or any database, for that matter), if you are deploying one with ClickOnce deployment as data, did you know if you open the database it changes the timestamp, and deploys a new version next time you deploy an update? On the client side, it then copies the previous version to the ApplicationData\pre folder, and puts the new one to the ApplicationData folder. On the reference to the in your project, set “Copy Local” to “true”. Set the Build Action to “Content”, and “Copy to Output Directory” to “copy always” on these entries in Solution Explorer. If you are using 3.0, substitute “30” for “35” in the names of these dll’s. You should be able to find them in C:\Program Files\Microsoft SQL Server Compact Edition\v3.5 (or v3.0). In the interest of copy and paste and making your life easier, here are the 7 dll’s you need to locate and add to your project.
#MICROSOFT SQL SERVER COMPACT 3.5 SP2 UPDATE#
At least one of them will be out of town, and when they come back, they’ll have too much e-mail to deal with and won’t take the time to follow your instructions to update their application.Ī better idea is to deploy the assemblies required locally. He must also have administrative privileges.Īdditionally, version control is more difficult with ClickOnce deployment, because prerequisites are not handled by the incremental updates, and you can never get all of your customers to reinstall a prerequisite. You can deploy it as a prerequisite, but this requires the customer to install one more thing without clicking Cancel.
#MICROSOFT SQL SERVER COMPACT 3.5 SP2 SOFTWARE#
If you are using a SQLServer Compact Edition database, you will need to deploy the software for it.