DispositionTypeNames Class

 
System_CAPS_noteNote

The .NET API Reference documentation has a new home. Visit the .NET API Browser on docs.microsoft.com to see the new experience.

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

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

System::Object
  System.Net.Mime::DispositionTypeNames

public ref class DispositionTypeNames abstract sealed 

NameDescription
System_CAPS_pubfieldSystem_CAPS_staticAttachment

Specifies that the attachment is to be displayed as a file attached to the e-mail message.

System_CAPS_pubfieldSystem_CAPS_staticInline

Specifies that the attachment is to be displayed as part of the e-mail message body.

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.

static void CreateMessageInlineAttachment3( String^ server, String^ textMessage )
{

   // Create a message and set up the recipients.
   MailMessage^ message = gcnew MailMessage( L"jane@contoso.com",L"ben@contoso.com",L"An inline text message for you.",L"Message: " );

   // Attach the message string to this e-mail message.
   Attachment^ data = gcnew 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 = gcnew SmtpClient( server );
   client->Credentials = dynamic_cast<ICredentialsByHost^>(CredentialCache::DefaultNetworkCredentials);
   client->Send( message );
   data->~Attachment();
   client->~SmtpClient();
}


.NET Framework
Available since 2.0

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

Return to top
Show: