tag:blogger.com,1999:blog-4366671410070576626.post7108837393051215020..comments2011-02-14T20:47:44.219-03:00Jose Gallardohttp://www.blogger.com/profile/06990898488326736094noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4366671410070576626.post-57064462335856208002008-02-15T23:20:00.000-02:002008-02-15T23:20:00.000-02:00Thanks Nick for your contribution. You're absolutely right, that is a very good option if you just need to deploy SQL Server Compact Edition with your app.<BR/>It's nice to have you here! Hope hear from you again soon.Jose Gallardohttp://www.blogger.com/profile/06990898488326736094noreply@blogger.comtag:blogger.com,1999:blog-4366671410070576626.post-38403504413118624722008-02-15T21:46:00.000-02:002008-02-15T21:46:00.000-02:00One option with SQL Server Compact Edition is to simply deploy the engine dlls alongside your application. This is the cleanest/simplest way to deploy SSCE as it means you never have to worry about dependencies during install or uninstall. <BR/><BR/>There are of course some penalties in this deployment strategy. Of course if there are multiple applications using SSCE then it would make sense to install it in the GAC for all applications to use but imho it's not worth the additional headache for deployment.<BR/><BR/>Hopefully the new Sync Services framework, which we are hoping will have a device implementation soon, will also deploy this way (ie either via installer or through assembly deployment)Nick Randolphhttp://community.softteq.com/blogs/nicknoreply@blogger.com