1

Closed

Change Accounts.dat file to XML

description

Now that I have a better grasp of XML, I think the Backup issue can be solved by moving away from a blob of binary data, and switching instead to a LINQ XML schema in code and file so that storing the accounts can still be protected (encrypt then Base64 encode), but be less likely to be destroyed by 1 or 2 bad bytes in a file. The affected account might be destroyed, but the WHOLE FILE wouldn't be destroyed. This is safer, more flexible, more fixable (in many instances, not all), and allows the user to side-backup/side-load accounts in the file as he/she sees fit. Since the data will be XML, the contents of the file can be backed up using anything that can store large blocks of text, which is easier to deal with as a developer AND as a user, and can even be better compressed for portability.
Closed Aug 20, 2013 at 5:15 AM by dsparksColossus
Accounts.XML now the default file, but importing of Accounts.Dat file in the program directory, or any other Accounts.XML file created by this version of the program is available.

comments

dsparksColossus wrote Aug 14, 2013 at 8:07 PM

In the process of writing and confirming the routines used to store and retrieve the account information from encrypted XML, and the routines to import a legacy "Accounts.dat" file in the new version, so that users can get their old account data without having to take screen shots of the barcodes, or writing down all of the account details for any stored accounts. The process of import should be straightforward and relatively painless, and the new Accounts.XML file should be more robust against data errors.

dsparksColossus wrote Aug 15, 2013 at 3:21 AM

The process seems pretty stable now. I expect to push out the updated version by the weekend.

wrote Aug 15, 2013 at 3:21 AM

wrote Aug 20, 2013 at 5:15 AM

wrote Aug 20, 2013 at 5:15 AM

wrote Aug 20, 2013 at 5:15 AM