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. ![]() 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. If you are using a SQLServer Compact Edition database, you will need to deploy the software for it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |