I’m not exactly sure what you are referring to when you say “the service”, so I’ll assume you mean a WCF service out of BizTalk. There is no need for any WSE 3.0 components. WCF already provides support for MTOM and the WS-Security protocol (see wsHttpBinding). If you need exact compatibility with an existing WSE 3.0 client, you can create a custom WCF binding for that. If you are not talking about a BizTalk service, I would strongly push you to use WCF for the same reasons, except that you’d obviously be writing the service with regular .NET code. WSCF can be used to create WSDL which can in turn be converted to a WCF service interface with svcutil.exe from .NET 3.0/3.5.

I hope that helps. Thanks, Tom

I noticed that you have some passing familiarity with WSCF. I’m using it on a customer project, and wondering if there’s some way you know of to add the WSE 3.0 pipeline to the service’s stack — so I can get turnkey security and MTOM.

Any idea if this is possible?

Thanks

Josh

josh.korn (at) diligentsia.com