WPF or ASP.NET as WCF Client -


i new wcf , going through tutorials right now. wondering benefits , disadvantages of using wpf or asp.net web application client service. understand depend on kind of service, besides common difference of 1 being windows app , other web application, advantages of 1 on other.

first of all, choice of client technology not depend @ on kind of service talking to. both wpf/winforms , web app capable talk web service.

instead, choice of client technology should purely driven requirements on client side

factors should consider when coosing 1 client technology on other are:

  • know-how available (and team)
  • deployment scearios: how app users, etc.
  • client environment: how many oss need support, how many different browsers have support when doing web app?
  • do have connected scenarios, or need privileged access client resources? - tip scale towards rich client.

even so, in many cases web app appears valid option have access wealth of non-ms tech javascript frameworks, css resources etc. etc.

on personal note: not use wcf define web services - there fantastic open source frameworks, notably servicestack make more productive , concentrate on service , less on mechanics , abstractions.


Comments

Popular posts from this blog

routing - AngularJS State management ->load multiple states in one page -

python - GRASS parser() error -

json - Gson().fromJson(jsonResult, Myobject.class) return values in 0's -