Issue with DefaultAccountManager.CS

[azure-samples]

Issue with DefaultAccountManager.CS

[matthchr]

Hi @shimail1 - thanks for the report.
I was able to reproduce the issue and fixed the FileLength 0 issue (see: #114), but I can't observe it happening on first BatchExplorer startup.

The old code was:

            if (!File.Exists(accountFileName))
            {
                using (var myFile = File.Create(accountFileName))
                {
                }
                await this.SaveAccountsAsync().ConfigureAwait(false);
            }

According to this though, it shouldn't be possible to get an empty accounts.xml if the file doesn't exist - since we do await this.SaveAccountsAsync().ConfigureAwait(false) which writes the default content. Do you by chance know how there got to be an empty accounts.xml file there in the first place? Possibly from an older version of BatchExplorer, or created manually?

In any case, the issue should be resolved now.

[ahmedgillanione]

empty accounts.xml file gets created when developer executes the code first time and because the code creates the file in the app data folder but due to exception quits the loop therefore the xml insert does not happen and file remains empty. and next time when the code runs it see the file exists but again generates exception.

[matthchr]

This issue resolved by #114