I read a lot of questions about how to update the database for the developer, etc., and I am inclined to use migratordotnet or something similar, however it seems that the updates should start with something like MSBuild or NAnt. This is not what I should expect from the end user.
Ideally, the process should be that the user installs a new version of the application, launches it and takes care of everything behind the scenes. Depending on how long the process takes, I may or may not show a progress bar, and then do it, the application, as a rule, blissfully does not realize that there are such things as sql, msbuild, a relational database or something even remotely technical sound.
Other information:
SQLCE installed by xcopy.
A single-user database, which most likely should not be too large.
Releases will be quite frequent if the program develops through user input for the requested functions.
The initial version is not yet complete, so there is no need to worry about any current data, you just need a painless process for the initial and subsequent releases (for the end user, preferably for me!).
Using LINQ to SQL as an ORM. (I have to upgrade the database first, then run SQLMetal to restore the classes?)
Running TDD (for the first time) and wondering how to automate update testing.
Visual C # Express, so VS plugins.
Edit:
, MSBuild .NET Framework, VS, , , migratordotnet msbuild. , , , , , , , .