It's seems to me that a restful one would be the simplest in terms of usage for all the clients (various tools and programs within the organisation).
Personally I find them easier to work with when coding to them as clients, and I'll be writing the first client for this service too. regards, Preet, in Auckland NZ On 6 June 2016 at 23:46, Greg Keogh <[email protected]> wrote: > Have you decided on the style you need: SOAP and XML, or RESTful? -- *GK* > > On 6 June 2016 at 21:20, Preet Sangha <[email protected]> wrote: > >> I've been out of .net Web stuff for many years and now need to build a >> webservice with a sql backend. I've seen many posts on here from you guys >> going web stuff and wondered if you could point me in the right direction >> please? >> >> If I wanted to build .net based web cased service, would I need to use >> WCF? Or is ASP.NET sufficient? If the latter what ASP.NET technology >> should I be researching? >> >> For the DB I suspect the latest entity framework will be sufficient but >> am open to ideas about other technologies that might not have been present >> when I last worked with it 5 years ago. >> >> This service will only be used in house, but might be housed in the cloud >> and security is a very high consideration. >> >> regards, >> Preet, in Auckland NZ >> >> >
