I have a desktop application in C# following the MVVM pattern that I need help flushing out a few remaining issues.
1. This is a desktop application that will not have access to the internet and needs a local database. I need to determine, and then implement the underlying database that will be used. For development, I used MS SQL, but I think perhaps a light weight file based DB might be more appropriate (think sqllite). The application uses a runtime WCF service to abstract the database now so I just need help selecting and implementing a database of choice behind it. I'm a MSSQL guy, and have little if any experience with other database types. I'm looking for a developer with experience with desktop applications who can tell me the best course of action here based on real world experience implementing and maintaining applications. I want to avoid a costly mistake due to my inexperience.
1b. After choosing this database, how can we create a backup/restore process for it such that re-installing this application on another PC is a smooth process. If the database is nothing more than a single file it's no issue of course presumably.
2. I have no experience with real desktop application installers. I need to setup my project to have a proper installer/uninstaller. This is particularly important with the database we choose which in theory has to be configured at install time.
3. There might be a few other items I will need help with, perhaps adding a few views for certain tasks etc. How about backup/restore? I need to implement an import/export data screen for certain. Frankly, I'm a back-end guy, so GUI applications are not my strong point. I can do the actual data work if somebody can show me how to wire up the view etc.
I'll try and update this project with more detail as I think of them.
Skills: mvvm-entity-framework, import