Update: After dariom’s reply, I think Just to mention, I did this in .net 2.0
>Avoid using data types that are not easily serializable or incompatible with the WS standard (so you will not be able to use the service in different languages) The most notable are RecordSets and other MS-only reference types.
>Please note that there is a difference between static web services (with static methods of [webmethod]) and non-static (memeber functions). This may be Affect your performance and resource usage.
>There is a difference between a .NET web service designed to run inside an intranet and a web service designed for the Internet. The second one should be simpler because the XML data on the wire should Much smaller.
>I think the web service will be deployed on the IIS server. Please note that the authentication will be different when running on the Intranet and the Internet. You may need to use impersonation to enable the service to perform specific tasks.
I think there are more and better looking for some documents discussing it.
I plan to write a program called api web service, it is developed with .Net and SQLServer. .Net provides a simple way to create web services by creating asmx files. But I need to know how to best design it or create web in .net Service best practices or some pointers to good articles, because this is my first experience in web service programming. Although SF has many references (very good) about API best practices, I can’t find A lot of information for .net webservices.
Update: After dariom’s reply, I want to mention that I am in .net 2.0 Doing this
It is not easy to remember all the best practices there, but here is my suggestion:
>Avoid using data types that are not easily serializable or incompatible with the WS standard (so you will not be able to use the service in a different language). The most notable are RecordSets and other MS-only reference types.
>Please Note that there is a difference between static web services (static methods with [webmethod]) and non-static (memeber functions). This may affect your performance and resource usage.
>Design .NET to run inside the intranet There is a difference between web services and web services designed for the Internet. The second one should be simpler because the XML data on the wire should be much smaller.
>I think the web service will be deployed on the IIS server. Please note , When running on Intranet and Internet, authentication will be different. You may need to use impersonation to enable the service to perform specific tasks.
I think there are more, better looking for some discussion about it Documents.