Closed marked23 closed 6 months ago
I'm using DFM 6.3.1 and Azurite. My isolated durable function project is running locally in VS 2022 debugger.
I have a DateTimeOffset property in a Durable Entity.
public DateTimeOffset? LastRunStartDate { get; set; }
I have a reset method to set the date explicitly:
public Task Reset() { LastRunStartDate = DateTimeOffset.Parse("2023-04-01 12:00:00 AM +00:00"); return Task.CompletedTask; }
After setting the date, I check the table in Azure Storage Explorer. Looks correct.
Then I check the display in DFM. The date has been changed to the equivalent moment in my time zone. However the "Z" indicates that this is still UTC.
I expected the date to be displayed as it was stored.
Thanks for reporting this, and here is the offending line.
Looking into what can be done to fix it...
Done in v6.4. Pls, validate.
I'm using DFM 6.3.1 and Azurite.
My isolated durable function project is running locally in VS 2022 debugger.
I have a DateTimeOffset property in a Durable Entity.
I have a reset method to set the date explicitly:
After setting the date, I check the table in Azure Storage Explorer. Looks correct.
Then I check the display in DFM. The date has been changed to the equivalent moment in my time zone. However the "Z" indicates that this is still UTC.
I expected the date to be displayed as it was stored.