{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 再贱就再见 的问题《web service / wcf service, is it ever better to re》','https://www.manongdao.com/q-649619.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
So from what I've seen about services, custom objects seem to be the way to go when the service is written to return data. If I am writing a service that will be used to 1) populate a database, or 2) provide information for a web site, is there ever a use for returning a dataset/datatable as opposed to a list of custom objects with all of that information?
thanks
Custom objects make it easier on your clients. DataSets/DataTables make it easier on you.
I think that you should base your decision on who you want to make it easier on.