Last post May 01, 2012 04:36 AM by Steven Cheng - MSFT
Apr 30, 2012 09:04 AM|itechathi|LINK
Consider, I have running webservice for past 5 years for my application. Please Note, I have fully satisfied with the Webservice what we have now. Because It runs perfectly.
When i am going to migrate this webservice to WCF, I really want to know the reason for migration. Because the webservice running successfully with any failure for past 5 years.
I Accept , Any way we need work on Latest Technology. But for what reason WCF is best in my case.
Please Dont say Like,
>.WCF is more reliable and security than webservice
>.WCF can host is many server than webservice like IIS,WAS,...etc
>.WCF can access by http,https,tcp/ip,....etc than webservice
>.WCF has [ServiceContract] and [OperationContract] and webservice has only [Webservice] and [Webmethod]
>.WCF Supports XML,MTOM,Binary, but webservice supports XML,MTOM,DIME
Becaues My webservice running successfully with satisfied.
Still Why i want to my WCF?.
Please Help me out?.
Thanks & Regards,
Apr 30, 2012 09:45 AM|patuary|LINK
Here Abdul Sami_ gives a good WCF comparison with Web Service and .Net Remoting like:
--> Session Management
--> Exception Handling
Apr 30, 2012 12:37 PM|Angad Bhat|LINK
I guess it's a judgement call that you have to make. You should ask yourself 'what is the reason for migration'. Are there any requirements/enhancements that may require features offered by WCF. Are you happy maintaining this service? Is it difficult to
maintain/support this service? etc. etc.
If your anwer is 'no' to all the questions then i guess there is no need to migrate.
May 01, 2012 04:36 AM|Steven Cheng - MSFT|LINK
For your case, since you have the ASMX webservice implemented service working well, then migrating to WCF service will not be a high priority task.
IMO, the simplest and most important reason for migrating from ASMX webservice to WCF is as below:
* ASMX webservice is the traditional distributed service(for interop) component of .NET platform. Now the WCF is the new technology and it is the suggested one for building services on .NET platform. In future version of .NET framework, it is apparently
that WCF will be enhanced and more features will be added while for ASMX webservice, it will just be kept for backward compatible (and for existing applications built with it) and is not the key focus for the product teams (comparing to WCF).
* WCF is a super set of ASMX webservice. So what ASMX webservice can do can also be done via WCF, while WCF can do much more than ASMX webservices.
In short, if your service application will probably involve more advanced service communication/data transfer features(like ws-security ....), then it is surely good idea to migrate to WCF. Otherwise, you can feel free to keep your current ASMX webservice
BTW, in case you will do the migration, you can try creating some test WCF services which is compatible to the ASMX webservice. Thus, you can using your existing ASMX webservice clients to call the test WCF services so as to ensure they works quite the same
as the previous ASMX ones. Here are the MSDN reference about creating WCF service to be compatible with ASMX webservice clients:
#Interoperability with ASP.NET Web Services
#How to: Configure WCF Service to Interoperate with ASP.NET Web Service Clients