Timezone ignored when using specific Start/End overload on UpsertEventRequestBuilder

[kjlibsol]

var cronofy = new CronofyAccountClient("xxxxxxxxxx");
string calendarId = "yyyyyyyyyyyyy";

var eventBuilder1 = new UpsertEventRequestBuilder()
    .EventId(Guid.NewGuid().ToString())
    .Summary("Cancun 17-18 | " + DateTime.Now.ToLongTimeString())
    .Description("Event description")
    .Start(2019, 11, 04, 17, 00)
    .End(2019, 11, 04, 18, 00)
    .TimeZoneId("America/Cancun");

var eventBuilder2 = new UpsertEventRequestBuilder()
    .EventId(Guid.NewGuid().ToString())
    .Summary("Malta 17-18 | " + DateTime.Now.ToLongTimeString())
    .Description("Event description")
    .Start(2019, 11, 04, 17, 00)
    .End(2019, 11, 04, 18, 00)
    .TimeZoneId("Europe/Malta");

cronofy.UpsertEvent(calendarId, eventBuilder1);
cronofy.UpsertEvent(calendarId, eventBuilder2);

I would expect this to create appointments at the specified time in the specified timezones - but it seems anything you enter in this overload of start/end is interpreted as UTC time, because this is how they show up in my calendar:

Using DateTime for start and end does not have the same issue.

[kjlibsol]

It seems this is actually "by design", and the reason it works when supplying a datetime is because that is implicitly a local time (unless you explicitly set Kind).

https://docs.cronofy.com/developers/calendars-events/time-zones/#creating-and-updating-calendar-events

I kind of understand why you would make that design-choice, but I still find it counter-intuitive in the C# SDK, especially since it is not mentioned in the intellisense. :)