Hello again...
So I'll shamefully admit that I had not tried the snapshots and laziness got the best of me.
However, after today's update, I tried to modify the calendar settings and unfortunately, while I was trying different options (I couldn't get the path right, for some reasons) the following things were discovered.
- if you put invalid characters in the calendar path (for example "double quotes"), EVEMon crashes because of an unhandled exception. You can find the backtrace here.
- if you close MS Outlook and reopen it, then try to go and change the custom calendar, EVEMon crashes. Backtrace is here.
- (I'm done with crashing it
), if you can't get the calendar path right and you decide to give up and try to select "Use default calendar" again, you can't. Any attempted selection (including the Cancel button) will fail and a pop-up window will appear stating that the calendar path is invalid. Workaround: close the options windows by using the upper-right X button... or continue to guess the calendar path.
Lastly, and this is the root for the above "guessing" problem, EVEMon is not compatible with Outlook 2010. I assume that you have tested it using an earlier version.
After a quick snoop in the code, I saw that in EVEMon.Common.ExternalCalendar:OutlookAppointmentFilter.cs you are prefixing the given folder path with "\\Personal Folders" to create the absolute path. This is no longer true for OL 2010, as the calendars (and most of the internal foldering) have changed.
For example, if you have an account called "
foobar@live.com (Live Account)" and it contains a calendar called "Foo's calendar", then the absolute path is "\\
foobar@live.com (Live Account)\Foo's calendar". Because the "Personal Folders" root was dropped, it is impossible to use custom calendars with Outlook 2010 in the current versions.
As a tip for users who need to obtain the full path, switch to "Calendars" view, right click on the calendar and select "Properties..." and look at the "Location" field. Copy that, then add the calendar's name, separated by a backslash.
Hope all of this helps, and I pinky promise I'll test the new snapshot once these are fixed
