
| Visual Basic (Declaration) | |
|---|---|
Public Class AttachmentStream Inherits CodingStream | |
| Visual Basic (Usage) | Copy Code |
|---|---|
Dim instance As AttachmentStream | |
| C# | |
|---|---|
public class AttachmentStream : CodingStream | |
| Managed Extensions for C++ | |
|---|---|
public __gc class AttachmentStream : public CodingStream | |
| C++/CLI | |
|---|---|
public ref class AttachmentStream : public CodingStream | |
The AttachmentStream class represents a non-MIME attachment, which can either be Uuencoded or Yencoded, but is always read out as Uuencoded.
If you are getting messages that contain non-MIME attachments these attachments would be located in MessageStream.NonMime.Attachments. These attachments are also accessible in the MessageStream.Attachments collection.
If you are creating a message that contains non-MIME attachments this can be done several different ways. If the attachment is located on disk, simply create a new AttachmentStream, passing the filename of the file into the constructor. If the attachment is in any other type of Stream (such as a MemoryStream), simply create a new AttachmentStream passing this Stream into the constructor.
When creating an AttachmentStream the data will always be read out as a Uuencoded attachment. For this reason, a new AttachmenStream will be created with AttachmentStream.MimeEncoding = ContentEncoding.Uuencode. Changing this property could result in incorrect message structure.
This is the base class for MimeAttachmentStream, so all MimeAttachmentStreams are AttachmentStreams, though they have additional Mime headers and can have other encoding types.
System.Object
System.MarshalByRefObject
System.IO.Stream
Dart.PowerTCP.Mail.CodingStream
Dart.PowerTCP.Mail.AttachmentStream
Dart.PowerTCP.Mail.MimeAttachmentStream
Target Platforms: Microsoft .NET Framework 2.0