At CampSight a few weeks ago, we were lucky enough to have Mark Fussell from WSE team stop by and give a talk. With WSE 2.0, you can use HTTP, TCP, named pipes and custom transports; but WSE 3.0 can host in any process. The advice now is: when you need TCP, use WSE 3.0 to host ASMX. Oh, and the Wsewsdl3.exe utility can create proxies that work over TCP via the /type param. Plus WSE 3.0 adds new support for Kerberos tokens, WSI, System.Transactions WS-Addressing, WS-Trust, SecureConversation, and MTOM. Not that I've ever used DIME (I kinda cheated and went with sending base64 strings as cheesy as that might sound), there is an article named Write Secure Web Services which has some pretty good info mostly about using MTOM with WSE 3. I have watching the webcasts on upgrading from WSE 2 to WSE 3 on my TODO list because I'm curious what the WS-Security changes are. I'll blog about that later.
