Reenable AppVeyor CI Testing

[dsyme]

AppVeyor CI was configured to use the "nessos" appveyor project corresponding to this github project.

That has been changed temporarily (and somewhat accidentally) to a "dsyme" appveyor project but there are no azure storage keys listed for that CI so testing has to be disabled.

We should move to use a different account, connected to appropriate Azure resources. It's hard to determine if/how expensive that will be though.

[isaacabraham]

Hmmmm. How does / did it work if two CI builds were kicked off at the same time - did they create their own storage account / service bus?

[dsyme]

Hmmmm. How does / did it work if two CI builds were kicked off at the same time - did they create their own storage account / service bus?

I'm not sure. I think the nessos one was actually working OK though, I just accidentally disabled it. So it might be just a matter of setting the Azure account details.

Also not all the tests were being run in the nessos account (build.fsx was not being used, it was just building the solution and then running some of the tests).

[dsyme]

Here's the appveyor.yml as it used to be before PR #163

https://github.com/mbraceproject/MBrace.Azure/blob/66462aece0d455edea7ce9e7741fdafa770421f3/appveyor.yml

[isaacabraham]

I'm happy to set up a storage and service bus account that we use for CI integration tests etc. - will just need access to AV in order to put in the keys etc. I guess.