Markus Minichmayr

The case you specified is undefined. RFC 5545 states, that > The recurrence set generated with a "DTSTART" property value that doesn't match the pattern of the rule is undefined....

It's also possible to use `ComponentSerializer` instead of `CalendarSerializer`, which doesn't have the issue. ```cs val icalStr = (new ComponentSerializer()).SerializeToString(calendar); ```

Duplicate of or at least related to #406?

@rianjs Any thoughts? Feedback would be appreciated, so we know, whether it's worth the effort..

Issue still exists in 4.1.11. The problem appears if the compared dates represent the same instant but in different timezones. In this case the `CalDateTime.CompareTo` considers the values neither as...

Might be a duplicate of or at least related to https://github.com/rianjs/ical.net/issues/406.

Hi @ewertons, Thanks for the clarification and sorry for the late reply. Maybe I'm understanding this wrong, but to my understanding the underlying xio could be implemented in an asynchronous...

> I share your interpretation, and _Python_ with the `datetime` and `pytz` libraries create the same results Oh, good to hear. You mean regarding omitting vs ignoring recurrences, right? I...

Very interesting, thanks for testing! Obviously `2025-03-30 02:30:00+01:00` doesn't exist, so how to resolve this? * Ignore (aka discard) the entry as required in 1)? Not sure, but rather not....

@axunonb I don't think so. #680 improved the situation but I don't think the problem has been fully addressed. The cases with `FREQ` leading to nonexistent instants is covered by...