I am using the WebDAV .NET for Exchange API provided by IndependentSoft to create calendar events on Exchange from my client program. We need to support Exchange 2003, so I must use WebDAV instead of EWS. When I create a recurring event (assuming it doesn't recur forever), I am only able to access the master recurrence.
A WebDAV appointment URL usually looks like this:
https://< server >/exchange/< email >/Calendar/< title >-63347455037521940237437201708.eml
The URL for a single occurrence of the master would look like this:
https://< server >/exchange/< email >/Calendar/< title >-63347455037521940237437201708-< n >.eml
So one should be able to use the API to grab the address of the master recurrence and then lookup the nth occurrence accordingly. However, that is not the case, and Exchange complains about a nonexistent resource.
HOWEVER, if I go onto Outlook Web Access (OWA) for the account, and scroll through the calendar views such that the nth occurrence shows up, suddenly the resources (all occurrences up to at least the nth) are populated and available when I access it using the IndependentSoft API. I am guessing then that Exchange creates occurrences of a recurring event in lazy fashion.
My question then is, is there a raw WebDAV call or an Exchange resource property or a server setting I can set that forces Exchange to create all event occurrences of a recurring event (provided it does not recur forever)? My client program needs this feature to be able to manipulate occurrences of an event in automated fashion (without relying on manual OWA-forced occurrence population)