AFAIK not much has changed. I've been out of the area for a while too. Start with web api and only go to wcf if web api is insufficient which I doubt it will be.
DB side can depend on many things as you know like if you have an existing db you need to use, who manages the db (dba?), amount of data, more reads or more writes, table structure, etc. Azure SQL or (unlikely) another Azure storage mechanism may be an options. On Monday, 6 June 2016, Preet Sangha <preetsan...@gmail.com> 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 > >
