We're having problems getting example data to be read into Outlook, though it works fine in iCal on OSX and validates correctly using an OSS iCalendar validation app.

FYI I opened up an issue for the iCalCreator library too: https://github.com/iCalcreator/iCalcreator/issues/11

Comments

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna commented
Issue summary: View changes
coredumperror’s picture

coredumperror CreditAttribution: coredumperror commented
Status: Active » Closed (won't fix)

You're using a 7-year-old Microsoft product. They didn't give a shit about standards compliance back then, so I'm not at all surprised that you're having problems. My best suggestion would be to upgrade your Outlook client.

Since Date iCal is not at fault here, I'm going to close this issue.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna commented
Status: Closed (won't fix) » Closed (works as designed)

It turned out to be a misunderstanding of what was happening. The 'X-WR-CALNAME' property was added to the ics file because the "Exclude Calendar Name" option wasn't checked; this made Outlook attempt to create a whole new calendar, rather than import the event into an existing calendar. Thanks.

coredumperror’s picture

coredumperror CreditAttribution: coredumperror commented

Ah, good. I'm glad to hear that you solved the problem.

petergroft’s picture

petergroft CreditAttribution: petergroft commented

Check if Outlook is running in compatibility mode
Find the Outlook.exe file on your computer.
Right-click the Outlook.exe file, choose Properties, and then choose the Compatibility tab.
If any of the boxes on the Compatibility tab are checked, uncheck them, then choose to Apply > OK.
Restart Outlook.

Hope This Works,
Peter