This scenario was never previously supported as the Table Storage API looked like it only supported DateTimeOffset. However, it turns out that all it does it convert the datetime to UTC and save it (ie. the offsets are normalized away to UTC), which makes it compatible with usages of DateTime.
I've added the necessary slight munging to get it to work in this PR.
Fixes #12.
This scenario was never previously supported as the Table Storage API looked like it only supported DateTimeOffset. However, it turns out that all it does it convert the datetime to UTC and save it (ie. the offsets are normalized away to UTC), which makes it compatible with usages of DateTime.
I've added the necessary slight munging to get it to work in this PR.