OutlookTools: Import/Export from/to iCal/vCard/CSV

[water]

I just noticed that Outlook does not allow to import iCal events programmatically.
I might implement some of the iCalendar data format (RFC 5545) if someone is interested
Please post here or click the "Like" button if you think this is a good idea

Edit: For download please see my signature

Edited July 9, 2019 by water

[FrancescoDiMuro]

@water

It surely could be a good feature to add to your (already) amazing Outlook UDF

[Skysnake]

importing iCal would make my life a lot easier.

 

[water]

Hope I can soon provide an early alpha Version  

Edit: For download please see my signature

Edited January 22, 2019 by water

[Starstar]

Great idea

[water]

First alpha test script:

Edit: For download please see my signature

Edited January 22, 2019 by water

[water]

Version 0.1 released. Edit: For download please see my signature

ADDED:

• Supports the DURATION property

Edited January 22, 2019 by water

[water]

Please post example .ics files you would like to import to Outlook.
So I can check and add the properties still missing in my UDF.

[water]

Do you think it is sensible to implement a callback function so you can decide how to process each event from an iCal file?
An array holding the properties to create the Outlook event item would be passed to the function (read only) .
You can then decide how to continue processing by setting @error:

0 - Create the Outlook event item
1 - Do not create the Outlook event item - continue processing the next event
2 - cancel processing the iCal file and return to the calling function

 

[argumentum]

2 hours ago, water said:

think it is sensible to implement a callback function so you can decide how to process each event

Yeap  

[water]

Great WIll be added.

[water]

Version 0.2.0.0 of the UDF has been uploaded. Have fun

[water]

At the moment the UDF only supports "floating" DATE-TIME values as described in the RFC (Section 3.3.5. - FORM #1: DATE WITH LOCAL TIME).
Support for UTC will follow quite soon (Same section - FORM #2: DATE WITH UTC TIME).

Is there a need for FORM #3: DATE WITH LOCAL TIME AND TIME ZONE REFERENCE (e.g. DTSTART;TZID=America/New_York:19970714T133000)?

[argumentum]

6 hours ago, water said:

Is there a need for .......

If is within possibility, the more complete, the better  

[water]

I will do my very best

Next on the list:

• VCard import
• Putting everything together into a single UDF (iCal import, VCF import etc.) and rename the thing to OutlookTools.au3.
• Add timezone support

What do you think?

[FrancescoDiMuro]

@water

MVP is not enough 

[water]

[water]

On 9.2.2019 at 9:19 PM, water said:

Next on the list:

• VCard import
• ...

What do you think?

Which version of vCard (import contacts from vcf files) should I implement?

Version 2.1, date: 09/1996 - That's the format used by Outlook when you export a contact. https://web.archive.org/web/20120501162958/http://www.imc.org/pdi/vcard-21.doc
Version 3.0, date: 09/1998 - Defined in RFC 2426: https://tools.ietf.org/html/rfc2426
Version 4.0, date: 08/2011 - Defined in RFC 6350: https://tools.ietf.org/html/rfc6350

 

[Skysnake]

6 hours ago, water said:

Which version of vCard (import contacts from vcf files) should I implement?

I opened all the links, intending to read before giving my 2 cents worth, then in a moment of profound selfishness it came to me, use the Outlook compatible version

For me at least the logic is simple.  Since this is an Outlook UDF, with Outlook being the operative word, the choice should be the option that provides max Outlook compatibility.

Version 2.1

There. Said it.

 

 

PS, Why is your test.ics file generated as version 2.0? 

Edited February 25, 2019 by Skysnake
Added a smiley

[water]

That's what I would have voted as well

This site explains the version differences - does not seem too hard to implement