I had a folder created at startup with webviewpane layout plus some registry related code deployed. During execution, numerous folders are created on the fly. How can FolderNames property be set dynamically to cater for newly created folders?
Please note that these folders are created as sub-folders beneath root folders, and also want to retain webviewpane layout for these folders.
I had observed that Key.SetValue() does not write folder names, additionally retrieval Key.GetValue() throws invalid cast exception.
This sample allows you to process events of the Folders collection of the root folder. To process other folders, you should create an instance of OutlookFoldersEventsClass for each folder and connect the instance to the folder.
Set the ADXOlFormsCollectionItem.FolderNames property in the ProcessFolderAdd method, say the way I do it below:
public override void ProcessFolderAdd(object folder)
AddinExpress.OL.ADXOlFormsManager formsManager = (this.Module as NewFolderEvent.AddinModule).adxOlFormsManager1;
string folderName = "Personal Folders\" + (folder as Outlook.MAPIFolder).Name;
To get the full path of a folder in Outlook 2003 you can use the FolderPath property of the MAPIFolder object.
Solid framework for deep customization of Microsoft Office. Use solution templates,
visual designers and components to develop version-neutral, secure and easy deployable extensions for all Office versions.
Supported Office extensions
COM add-ins, Outlook plug-ins, RTD servers, smart tags, Excel XLL and UDF
This technology is now available for our custom development services only. Based on the Add-in Express for Office core, it is designed for building custom-tailored Office add-ins with far less coding than you usually have to do. Plus, it includes all Add-in Express features such as True RAD, visual designers, Outlook view and form regions, etc.
Extensions: VSTO-based application-level Office add-ins
Applications: Outlook, Excel, Word, PowerPoint, Visio, InfoPath
Office versions: 2003, 2007, 2010 (x86 and x64)
IDE: VSTO 2005 SE, 2008, 2010; VB.NET, C#
for Microsoft® Office and Delphi® VCL
Get the best platform for building version-neutral, fast and easy deployable plug-ins by using Add-in Express projects templates, visual designers, components and wizards in combination with a perfect Delphi compiler.
Supported Office extensions
COM add-ins, Outlook plug-ins, smart tags, Excel RTD and UDF
This is an extension for Visual Studio that allows developers to quickly create WiX-based setup projects in a familiar Visual Studio way.
The Designer for WiX Toolset lets you forget the plain Windows Installer XML and concentrate on your deployment logic. It integrates several editors with the Visual Studio IDE and provides a set of vdproj designers to configure the file system, registry, user interface, custom actions, launch conditions and more for your setup projects.
Visual Studio versions: 2010, 2012, 2013, 2015, 2017, 2019
This technology is now available for our custom development services only. This visual toolkit allows creating secure, managed, isolated, deployable and version-neutral plug-ins for Outlook Express and Windows Mail. It provides powerful solution templates, Outlook Express - specific components, visual designers and wizards for advanced customization of Outlook Express menus, toolbars, panes and regions.
Extensions: Outlook Express plug-ins
Versions: Outlook Express 6.x, Windows Mail 6.x
IDE: VS 2005, 2008; VB.NET, C#, C++/CLI
The innovative technology for customizing Outlook views and forms. It is included in all Add-in Express for Office products and can be used to extend Outlook views, e-mail, task and appointment windows, To-Do bar, Reading and Navigation panes with your own custom sub-panes.
Extensions: application-level Outlook add-ins
Outlook versions: 2000, 2002, 2003, 2007, 2010 (x86 and x64)
.NET Edition: VS 2005, 2008, 2010; VB.NET, C#, C++/CLI
.NET Framework: 2.0 and higher
VCL Edition: Delphi 5 - XE
Microsoft and the Office logo are trademarks or registered trademarks of Microsoft Corporation in
the United States and/or other countries. All other trademarks are property of their respective owners.