MailAsAttachment Class
Merged Document To E-Mail Attachment.When the object is serialized out as xml, its qualified name is w:mailAsAttachment.
Inheritance Hierarchy
System.Object
DocumentFormat.OpenXml.OpenXmlElement
DocumentFormat.OpenXml.OpenXmlLeafElement
DocumentFormat.OpenXml.Wordprocessing.OnOffType
DocumentFormat.OpenXml.Wordprocessing.MailAsAttachment
Namespace: DocumentFormat.OpenXml.Wordprocessing
Assembly: DocumentFormat.OpenXml (in DocumentFormat.OpenXml.dll)
Syntax
'Declaration
Public Class MailAsAttachment _
Inherits OnOffType
'Usage
Dim instance As MailAsAttachment
public class MailAsAttachment : OnOffType
Remarks
[ISO/IEC 29500-1 1st Edition]
17.14.19 mailAsAttachment (Merged Document To E-Mail Attachment)
This element specifies that, after importing external data into fields to generate a series of destination WordprocessingML documents as e-mails, the resulting documents should be emailed as an attachment rather than the body of the actual e-mail.
If this element is omitted, then its value shall be assumed to be false (i.e. the destination source is not an e-mail attachment). If the destination element (§17.14.11) specifies that the merged document destination is not email, then this element shall be ignored.
[Example: Consider a merged WordprocessingML document that has been connected to an external data source containing three records and that contains the following WordprocessingML in its mail merge properties as follows:
<w:mailMerge> … <w:destination w:val="email" /> <w:mailAsAttachment /> … </w:mailMerge>
After the external data has been imported into the merged document's respective merge fields, three emails is generated (as specified by the destination element (§17.14.11) with a val attribute of email, each an attachment consisting of one of the three documents resulting from the mail merge result (rather than just including the merged document as the body of the email). end example]
Parent Elements |
|---|
mailMerge (§17.14.20) |
This element’s content model is defined by the common boolean property definition in §17.17.4.
© ISO/IEC29500: 2008.
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.