Rules for smooth migration to WCF

Is it really worth to move from WSE XML Web serivices to to Windows Communication Foundation (WCF) ?!

I would say, Yes. The benefits of migrating WSE 3.0 XML Web services to WCF are including increased performance and the support of additional transports, encodings etc… and complete support for WS-* specifications.

Are you building some distributed application and want to migrate to WCF later. Then the basic rules for smooth migration to WCF are:

For smooth migration to WCF from existing technologies, follow the below basic rules:-

- Build services using the ASP.NET (ASMX) Web service model.
- Enhance your ASMX service with WSE if you need the WSE feature set (including end-to-end security).
- Use object technology in a service’s implementation.
- Use System.Messaging if you need the reliable messaging and queuing features in MSMQ.
- In ASMX, avoid or abstract using low-level extensibility such as the HTTP Context object.
- In .NET Remoting, avoid or abstract using low-level extensibility such as .NET Remoting sinks and channels.
- In Enterprise Services, avoid passing object references inside of ES.
- Do not use COM+ APIs—instead, use System.EnterpriseServices.
- Do not use MSMQ APIs—instead, use System.Messaging.

Check here for more info on "Migrating WSE 3.0 Web Services to WCF "