I didn't see your source code (just planning to learn C# :)), but as I understand, as a simple user, you generate the .ics files from RC and do not allow Outlook to do this work. Maybe this is a way to solve the problem with the same title/description (I know about outlook guard). Here I found a short VB script that exports all data to .ics: http://www.informit.com/articles/article.asp?p=360066&seqNum=3&rl=1
The idea is to say Outlook to save calendar info into an .ics file and after that to open it with RC and to publish events to the internet. It seems that is not so hard to do this, what do you think?
I didn't know that that was possible...however, it'd be more simple but maybe it'd still miss some features...for example, both Outlook 2003 and 2007 are missing the feature to support as VTODO elements the TaskItems made in Outlook...instead, in this way, you can still export everything.
I don't even know what TimeZone support Outlook use...it's not Olson DB, however that would be even easier...
Googling around I found this tool with source code:
"Vzic can generate 'pure' timezone files which match the Olson timezone data exactly, or it can generate timezone files that are compatible with Microsoft Outlook (which is the default)"
So, will you try to include proposed export solution into the next RC version (solving title/description problem)? :)
Oops, sorry, the above message should be as responce to this one:
no, it's not that really the problem (besides that, using that program would require every machine to have an Olson DB...), but the fact RC has already got an his system to set the TimeZone, and I'm worried on how this would work...
However, the idea is interesting for the problem of the description of the appointments...I'm willing to give it a try (if you google around, you'll find out that a lot of people do hate the way Outlook creates the iCalendar)...I've to test it a bit :)
The problem is that taskItems wouldn't work yet...
Yeah, maybe you are right that Outlook creates .ics in his own way, BUT from the created files you can load only information you need, add missed info and publish iCalendar as RC does now, but with right description.
About MSDN remark:
If it is impossible to call SaveAs from RC without that warning, go the simplest way and call a VBScript instead. It will create required file without any stupid warnings (at least the script from given example does this perfectly from current session). Maybe it's strange but the most important for us are the results. ;)
Do you know if it's possible to call a VBScript through a normal C# application?
And I'm afraid that there would be still some problems: the Outlook Object Model is the same for plugins and macros I believe...
When you use the SaveAs method to save items to the file system, you receive an "address book" warning message. This includes all types of items, whether or not the items have attachments or active content. This change has been made so that someone cannot programmatically save items to a file and then parse the file to retrieve e-mail addresses.
Also note that even though olDoc is a valid OlSaveAsType constant, messages in HTML format cannot be saved in Document format, and the olDoc constant works only if Microsoft Word is set up as the default email editor.
That's the same thing that happens when you try to access directly to the description of an AppointmentItem -_-...