WCF provided much more features and functionality than asmx service out of the box e.g. it implements standards like WS Security, WS Addressing, WS Transaction etc. Performance wise its better than asmx services. See following links for WCF benefits:
http://msdn.microsoft.com/en-us/library/ff648122.aspx
http://msdn.microsoft.com/en-us/library/bb310550.aspx
http://msdn.microsoft.com/en-us/library/aa480190.aspx
For converting an asmx service to WCF we need to take following steps, This approach will choose appropriate serializer depending on the types defined in your asmx service.
- Create a .wsdl file from current asmx service, you can do this by typing the service url?wsdl in IE and then save the file as .wsdl extension
- Go to Visual Studio Command Prompt
- Go to the directory where you saved wsdl file and run svcutil.exe with wsdl file name as argument e.g. svcutil.exe Queue.wsdl
- The svcutil will generate two files .cs file and .config file. The .cs file will contain your service contract.
- Create a new WCF Service Application in your solution, This template creates a service1.svc in your project, remove all files associated with Service1
- Add a new WCF Service by using add item and name it as your own service e.g. Queue
- Delete the interface file created in above step.
- Copy your .cs file generated by svcutil to your WCF service application folder and include it in your project. Change the file name to indicate it as an interface e.g. IQueue.cs. You need to change the class name also and its references in the class.
- In your generated interface file, remove , ReplyAction = “*” string for each operation, see the screen shot:
- Implement the above interface in your implementation class
- Build your project, and you should be good to go.
- You can now implement your methods by copying your old code to new one or by writing it new.
- In order test, browse your service in browser or add a service reference to a test project, and it should generate similar interface at your end.
No comments:
Post a Comment