We need something better than a .pst file. I would prefer a SQL/MSDE database file that has less chance of going corrupt. I have seen this message box too many times and the tools scanpst.exe and scanost.exe do not fix it.

Cached Items in Outlook

When “Cached Exchange Mode” is enabled, items which have been cached locally will have some unexpected behaviour. This feature allows one to work with your personal folders, as well as selected public folder contents even when they’re disconnected from the Exchange Server.

However, once that feature is enabled, if you attempt to access the Parent.FolderPath property, you will be returned an inaccurate folder path. To see this bug in action, select an item in a subfolder of the folder which you have added to Favorites. Now press Alt+F11 to bring up the Visual Basic editor, followed by Ctrl+G to bring up the Immediate window.

Application.ActiveExplorer.Selection(1).Parent.FolderPath

This will return

'\\Public Folders\Favorites\ImmediateParentFolder'

One would assume it would return

'\\Public Folders\Favorites\ParentFolder\ImmediateParentFolder'

but that’s not the case. If you disable “Download Public Folder Favorites”, then the above code would return the correct canonical path of the folder.

'\\Public Folders\All Public Folders\ParentFolder\ImmediateParentFolder'

In our product SSW eXtremeEmails!, it prevents the Incident screen from obtaining a valid URL for the email item.

As a work around, the “Download Public Folder Favorites” settings should be disabled. If you wish to see correct URLs in your personal folders, “Cached Exchanged Mode” must be disabled all together.

I hope this would be fixed in the next version of Outlook. Items in folders added to Favorites should provide the canonical path to aid Outlook ‘smart client’ plug-ins with Offline functionality, even when “Download Public Folder Favorites” is enabled.

Item Enumeration

Outlook (probably for backward compatibility reasons) doesn’t have a default Outlook.Item object as the parent of the various Outlook.Items (Outlook.MailItem, PostItem, AppointmentItem). This means code like this wouldn’t work:

dim oItem as Outlook.MailItem
for each oItem in Outlook.ActiveExplorer.Selection
' you get errors for any items (like PostItem), that isn't an 
MailItem in your inbox
MsgBox oItem.Subject
next

Figure: Example of incorrect code

So you have to write something like this:

dim oItem as Object
for each oItem in Outlook.ActiveExplorer.Selection
' this will work, because every type of Outlook Item has the subject property... 
' but we're relying on reflection (late binding) here and 
' intellisense doesn't help us when we write code,
' compiler doesn't tell us if we made a typo,
' late binding is slower...
MsgBox oItem.Subject
next

Figure: Example of correct code

The current object model does not make for nice and easy plugin development. Some issues include:

Setting the title of the COM addin in the options page:

To set the title using VSTO you have to have code like this, which is rather unnatural:

[System.Runtime.InteropServices.DispId(-518)]
public string Caption 
{
	get {return "SSW eXtreme Emails";}
}

Throw out backwards compatibility and start a fresh. For example, you should be able to inherit the contacts page and change the way it looks and add extra functionality to it.

I want to know who created this contact and who updated the information for this contact, it should have “Created By” and “Updated By” fields.

Suggestion: Adding “Created By” and “Updated By” fields for contact information, and automatic save the logon user to the fields after a contact information was created or updated.

We have a rule better to interfaces about this, please see Data Entry Forms – The way to develop Data Entry Forms – Created/Last Updated By Fields