Wed 23rd May

It’s been a while! I just realised six months to the day since the last post.

Much has happened and much progress has been made.

More details and a release in the very near future!

Wed 23rd Nov

So I’ve spent half the day adding a game date to the bloody scoresheet. Date handling in JavaScript / JSON and MVC is a right pain in the arse. Throw in jQueryUI date pickers and knockout, and it’s just a complete clusterfuck.

Ended up being a fairly productive day, though worked until early hours of the morning. Grid system is shaping up nicely!

Tue 22nd November

Getting there! Got basic game statistics up and running. Still a lot of work to do, definitely a lot of cleaning up to do, but it’s starting to look like an application!

Fri 18th Nov

I guess not a lot happened last Friday…

Thu 17th Nov

Didn’t get much done today, was a fairly late, productive night last night. I have the wall of tasks set up, should work fairly well, all those sticky notes staring down at me, jostling with each other to be noticed. Well… At least I can move them around and tell them which ones need to be done before the next big release. Err… First big release. Uhh… First alpha release… Whatever, release.

Basic stats tomorrow, then very near to a release candidate anyways. Apart from all those little yellow sticky notes staring down at me.

Wed 16th Nov

A couple of responses on the stackoverflow question. One about the new version of the Azure SDK, released two days ago, apparently contains improved exception contracts. Downloading now, hopefully this is what is needed!

Got a little paranoid last night about backups not working. I know that the maximum file size for Windows Live Mesh is 50Mb, and some of the database backups are bigger than that. A new approach is needed. Got a workspace set up to get the entire source control repository to a backup folder that is synced with Live Mesh. Should work much better, but still got to sort out Windows Live Mesh running as a service properly.

Tue 15th November

Authentication today. This will support persistence of team list. As it is per user, it makes sense now to put this on the user object. This will probably change, particularly when we start to support multiple users for the same “account”.

Man. Table Storage exceptions suck balls. So bloody useful. Azure diagnostics look ridiculous to configure. I guess I’m going to have to at some point, may as well get them going.

So it looks like turning development storage logging on results in a stack more information. Why this doesn’t appear in the exception thrown, or at least have an option to return it, is beyond me. I’ll have to try Fiddler.

Posted on stackoverflow about exception messages. See what comes back.