Jonathan Gilbert

Okay, I added a test that I think encapsulates what you were talking about, and I tweaked the behaviour of the `Date` set to match the expectations encoded in the...

Let me know if that test covers the functionality you were thinking of. :-)

That's fair :-) For what it's worth, we've been running on a private prerelease build on our private Azure Artifacts server for, well, for some time now :-P

How's it going? :-)

Where are we at?

@bchavez Any chance of getting this loose end tied off? :-)

Oh, you know what, I was mistaken. We don't have a custom build of Bogus. We have a custom build of FluentAssertions with support for System.Data types. We just still...

I wonder if this would work: Always convert the start & end `DateTime` values to UTC, generate the bogus value in that range as a UTC `DateTime`, and then convert...

I have made a PR that doesn't add any new overloads or functionality, and simply converts the date range to UTC before calculating a random value, then converts the random...

I mean, it could be added as a separate overload so that existing calls keep going to the same method they've been calling all along, right?