FormRegionNameAttribute Class

Represents the name that uniquely identifies a form region across all Outlook add-ins.

Namespace: Microsoft.Office.Tools.Outlook
Assembly: Microsoft.Office.Tools.v4.0.Framework (in Microsoft.Office.Tools.v4.0.Framework.dll)

Inheritance Hierarchy

System::Object
System::Attribute
Microsoft.Office.Tools.Outlook::FormRegionNameAttribute

Syntax

C++

[AttributeUsageAttribute(AttributeTargets::Class, AllowMultiple = false, 
	Inherited = false)]
public ref class FormRegionNameAttribute sealed : Attribute

Constructors

	Name	Description
	FormRegionNameAttribute(String^)	Initializes a new instance of the FormRegionNameAttribute class.

Properties

	Name	Description
	Name	Gets a name that uniquely identifies the form region across all add-ins.
	TypeId	(Inherited from Attribute.)

Methods

	Name	Description
	Equals(Object^)	(Inherited from Attribute.)
	GetHashCode()	(Inherited from Attribute.)
	GetType()	(Inherited from Object.)
	IsDefaultAttribute()	(Inherited from Attribute.)
	Match(Object^)	(Inherited from Attribute.)
	ToString()	(Inherited from Object.)

Explicit Interface Implementations

	Name	Description
	_Attribute::GetIDsOfNames(Guid%, IntPtr, UInt32, UInt32, IntPtr)	(Inherited from Attribute.)
	_Attribute::GetTypeInfo(UInt32, UInt32, IntPtr)	(Inherited from Attribute.)
	_Attribute::GetTypeInfoCount(UInt32%)	(Inherited from Attribute.)
	_Attribute::Invoke(UInt32, Guid%, UInt32, Int16, IntPtr, IntPtr, IntPtr, IntPtr)	(Inherited from Attribute.)

Because Outlook can load more than one add-in and each add-in can contain multiple form regions, you should ensure that the Name property of the FormRegionNameAttribute class is set to a unique name to avoid a name collision.

When you add an Outlook Form Region item to the project, Visual Studio automatically adds this attribute to the form region factory class in the form region code file. It sets the name of the attribute to the add-in name plus the form region item, separated by a dot—for example, "OutlookAddIn1.FormRegion1".

Thread Safety

Any public static ( Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.