I am trying to use the SMTP adapter to send an XML file through email once i
f
goes through an orchestration.  The process works nicely, however it puts th
e
XML text in the body of the email instead of sending the XML as an
attachment.  Is there a way to change this?

[ Post a follow-up to this message ]

Dave:

Create a Send Pipeline. Crag-drop the MIME/SMIME Encoder Pipeline Component
from the toolbox onto ur Encode stage. Set the property "Send body part as
attachment" to true.
Use this new pipeline with ur SMTP send ports.

Regards
Dev

"Dave" <Dave@discussions.microsoft.com> wrote in message
news:7C8B008E-64F9-4A72-883D-2A4562DF65D5@microsoft.com...
> I am trying to use the SMTP adapter to send an XML file through email once
if
> goes through an orchestration.  The process works nicely, however it puts
the
> XML text in the body of the email instead of sending the XML as an
> attachment.  Is there a way to change this?

[ Post a follow-up to this message ]

Thanks, that worked for sending the attachment.  How do I set the file name
and extension so it will show up as an XML file?  It attached with a generic
name "Attachment0" in text format.  The file looked good though when I opene
d
it in notepad.


"Devdutt Patnaik" wrote:

> Dave:
>
> Create a Send Pipeline. Crag-drop the MIME/SMIME Encoder Pipeline Componen
t
> from the toolbox onto ur Encode stage. Set the property "Send body part as
> attachment" to true.
> Use this new pipeline with ur SMTP send ports.
>
> Regards
> Dev
>
> "Dave" <Dave@discussions.microsoft.com> wrote in message
> news:7C8B008E-64F9-4A72-883D-2A4562DF65D5@microsoft.com... 
> if 
> the 
>
>
>

[ Post a follow-up to this message ]

Dave:
Try this:

1) Create a custom pipeline component.
2) Modify the Execute() method of this component, to look like this:

public Microsoft.BizTalk.Message.Interop.IBaseMessage
Execute(IPipelineContext pc, IBaseMessage inmsg)

{

string strAttachmentFileName = "Dave.xml";


inmsg.Context.Write("FileName","http://schemas.microsoft.com/BizTalk/2003/mi
me-properties ", strAttachmentFileName );

return inmsg;

}

3) Use this custom pipeline component, in the custom pipeline that you have
developed earlier. But put this component in a stage prior to the encoding
stage. The MIME/SMIME encoder should use this FileName property while
creating an attachment.

See if this works, otherwise I'll suggest something else.

Regards
Dev


"Dave" <Dave@discussions.microsoft.com> wrote in message
news:DCE50F1B-7088-499C-BE82-EFF2C89BE4B6@microsoft.com...
> Thanks, that worked for sending the attachment.  How do I set the file
name
> and extension so it will show up as an XML file?  It attached with a
generic
> name "Attachment0" in text format.  The file looked good though when I
opened[vbcol=seagreen]
> it in notepad.
>
>
> "Devdutt Patnaik" wrote:
> 
Component[vbcol=seagreen] 
as[vbcol=seagreen] 
once[vbcol=seagreen] 
puts[vbcol=seagreen] 

[ Post a follow-up to this message ]

Was your issue solved by the information provided?

Regards
Dev

"Dave" <Dave@discussions.microsoft.com> wrote in message
news:DCE50F1B-7088-499C-BE82-EFF2C89BE4B6@microsoft.com...
> Thanks, that worked for sending the attachment.  How do I set the file
name
> and extension so it will show up as an XML file?  It attached with a
generic
> name "Attachment0" in text format.  The file looked good though when I
opened[vbcol=seagreen]
> it in notepad.
>
>
> "Devdutt Patnaik" wrote:
> 
Component[vbcol=seagreen] 
as[vbcol=seagreen] 
once[vbcol=seagreen] 
puts[vbcol=seagreen] 

[ Post a follow-up to this message ]

>-----Original Message-----
>Dave:
>
>Create a Send Pipeline. Crag-drop the MIME/SMIME Encoder
Pipeline Component
>from the toolbox onto ur Encode stage. Set the
property "Send body part as
>attachment" to true.
>Use this new pipeline with ur SMTP send ports.

Hello Dave (and others!).

I've been looking at this example provided by MS:

http://support.microsoft.com/default.aspx?id=326300

I trying to build the solution on my own workstation using
VS2003.NET and then install it on our BizTalk server. No
success so far.

I get some warnings like this one (when trying to run some
of the commands):

"TlbExp warning: Referenced type is defined in managed
component, which is imported from a type library that
could not be loaded because it was not registered
(type: Interop_PipeComplib.IPipelineComponent; component:
 c:\winnt\assembly\gac\interop_pipecompli
b\1.0.0.0__8de4f0e2
8861c1ac\interop_pipecomplib.dll)."

I got a co-worker who says he can't send files with
attachement (becomes inline when recieved) - and when I
then saw this thread I wondered if there's an much easier
solution than the one we're attempting using the linked
example?

If possible please reply to smi*@*systemate.dk (removed
the 2 "*"). Thanks in advance.

[ Post a follow-up to this message ]

Dev, I am still working on it.  I haven't written any custom pipeline
components yet, so I am trying to figure that one out now.  I appreciate you
r
help.

"Devdutt Patnaik" wrote:

> Was your issue solved by the information provided?
>
> Regards
> Dev
>
> "Dave" <Dave@discussions.microsoft.com> wrote in message
> news:DCE50F1B-7088-499C-BE82-EFF2C89BE4B6@microsoft.com... 
> name 
> generic 
> opened 
> Component 
> as 
> once 
> puts 
>
>
>

[ Post a follow-up to this message ]