D
Dorell
Hi
I'm learning how to create Form Regions by following the MSDN article at
http://msdn.microsoft.com/en-us/library/bb226713.aspx but the form is not
loading when I try to debug the add-in. I've had some difficulties trying to
follow the article because I'm using VSTO 3.0 in VS 2008 but the article is
using VS 2005 with a custom template.
The add-in complies and runs, but no adjoining region appears when I open a
message. I have tested the GetFormRegionStorage and BeforeFormRegionShow
methods with Debug statements but nothing happens, so I'm assuming that
Outlook is not finding the FormRegionStartup interface. I have implemented
this interface in the ThisAddIn class instead of the Connect class in the
template. I have tried implementing the IDTExtensibility2 interface as
described in the article and nothing happens (Does the IDTExtensibility2
interface need to be implemented in a VSTO 3.0 add-in to load a form region,
or is only FormRegionStartup needed?)
I've checked the registry entry in the IPM.Note key that points to the form
region manifest file, and the addin element in the manifest file that
contains the key name of the add-in that contains the corresponding business
logic and FormRegionStartup interface, but didn’t find anything wrong.
Can anyone offer assistance, or point me in the right direction for
resolving the issue?
Regards,
Jason
I'm learning how to create Form Regions by following the MSDN article at
http://msdn.microsoft.com/en-us/library/bb226713.aspx but the form is not
loading when I try to debug the add-in. I've had some difficulties trying to
follow the article because I'm using VSTO 3.0 in VS 2008 but the article is
using VS 2005 with a custom template.
The add-in complies and runs, but no adjoining region appears when I open a
message. I have tested the GetFormRegionStorage and BeforeFormRegionShow
methods with Debug statements but nothing happens, so I'm assuming that
Outlook is not finding the FormRegionStartup interface. I have implemented
this interface in the ThisAddIn class instead of the Connect class in the
template. I have tried implementing the IDTExtensibility2 interface as
described in the article and nothing happens (Does the IDTExtensibility2
interface need to be implemented in a VSTO 3.0 add-in to load a form region,
or is only FormRegionStartup needed?)
I've checked the registry entry in the IPM.Note key that points to the form
region manifest file, and the addin element in the manifest file that
contains the key name of the add-in that contains the corresponding business
logic and FormRegionStartup interface, but didn’t find anything wrong.
Can anyone offer assistance, or point me in the right direction for
resolving the issue?
Regards,
Jason