Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
DispositionTypeNames Class

DispositionTypeNames Class

Supplies the strings used to specify the disposition type for an e-mail attachment.

System.Object
  System.Net.Mime.DispositionTypeNames

Namespace:  System.Net.Mime
Assembly:  System (in System.dll)

public static class DispositionTypeNames

The DispositionTypeNames type exposes the following members.

  NameDescription
Public fieldStatic memberAttachmentSpecifies that the attachment is to be displayed as a file attached to the e-mail message.
Public fieldStatic memberInlineSpecifies that the attachment is to be displayed as part of the e-mail message body.
Top

The values in this enumeration can be used to set the DispositionType property for an e-mail attachment. The information in the ContentDisposition class represents the MIME Content-Disposition header. This header is described in RFC 2183 available at http://www.ietf.org.

The following code example sets the disposition type for an attachment.

		public static void CreateMessageInlineAttachment3(string server, string
		textMessage)
		{
			// Create a message and set up the recipients.
			MailMessage message = new MailMessage(
			   "jane@contoso.com",
			   "ben@contoso.com",
			   "An inline text message for you.",
			   "Message: ");

			// Attach the message string to this e-mail message.
			Attachment data = new Attachment(textMessage, MediaTypeNames.Text.Plain);
			// Send textMessage as part of the e-mail body.
			message.Attachments.Add(data);
			ContentDisposition disposition = data.ContentDisposition;
			disposition.DispositionType = DispositionTypeNames.Inline;
			//Send the message. 
			// Include credentials if the server requires them.
			SmtpClient client = new SmtpClient(server);
			client.Credentials = (ICredentialsByHost)CredentialCache.DefaultNetworkCredentials;
			client.Send(message);
			data.Dispose();
		}

.NET Framework

Supported in: 4.6, 4.5, 4, 3.5, 3.0, 2.0

.NET Framework Client Profile

Supported in: 4, 3.5 SP1

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