TimeZoneInfo field serialized differently on Windows vs Linux agent in Azure #809
verynewuser
started this conversation in
General
Replies: 1 comment 1 reply
-
can u try v 19.11.0 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a class having a property of
TimeZoneInfo
type. Callingawait Verifier.Verify(obj)
on it generates a *.Received.txt file, in which the value for this property is different when I test it on my development environment as compared to what it evaluates on Azure DevOps. My development environment is Windows and the Azure agent is Linux. On my local the object is serealized as{ timeZone: AUS Eastern Standard Time }
whereas on Azure it is serialized as
{ timeZone: Australia/Sydney }
This behavior causes the test to fail in build pipeline. I have a temporary workaround which is to call
.ScrubMembersWithType<TimeZoneInfo>()
in a fluent-style, but is there a better way to tackle this?Beta Was this translation helpful? Give feedback.
All reactions