I have been a C# developer for a while now and have hear a lot of buzz
about web services. I would like to try incorporating a web service in
a new application I am developing, but have no clue where to start. I
have tried checking out the Web Service Factory by Microsoft Patterns &
Practices but its a bit overwhelming. A couple of key questions I
have:
Is it general practice to separate service roles into separate services
or just include all functionality in one? For example, if I have a
simple customer, products, and order database set up. Would I create
different services to operate on customers, orders, and products or
build one service for everything?
Another thing I have noticed is MSSQL Server 2005 has a new thing
called SOAP Endpoints. To use or not to use?
Any pointers would be greatly appreciated. Thanks in advance!
WishMaster - 31 Jan 2007 04:58 GMT
On Jan 26, 5:20 pm, bennyandli...@gmail.com wrote:
> I have been a C# developer for a while now and have hear a lot of buzz
> about web services. I would like to try incorporating a web service in
[quoted text clipped - 13 lines]
>
> Any pointers would be greatly appreciated. Thanks in advance!
Hi Bennyandli,
I think unfortunately you jumped in advanced topics i.e. MS Service
Factory and SOAP Endpoints.
First of all you need to understand the concept and creat some basic
web services and then move to advance concepts.
If you have experince in C# then Web Service will be very easy for
you. All code and concepts are same as for as coding concern BUT web
services by nature are diffrent (well I would say intersting).
Hope, once you familer with web Services you will enjoy working with
them.
Following are few link where you can start:
Concepts: http://alistapart.com/articles/webservices
Creating basic web service: http://www.codeproject.com/cs/webservices/
myservice.asp
Cheers,
Amer
MCSD.Net
ITIL Certified