How to setup WCF -
i went through many posts but, did not able clear of basic doubts related wcf service follow:
why should maintain separate class library projects assembly service.contracts
, service.implementation
? can implement 1 interface multiple times in single assembly. suppose create - wcf application project , maintain interfaces separate folder , svc.cs file separately.
add service reference not alternative adds schemas client side. svcutil.exe same thing. then, best way consume wcf service @ client side ?
all explained in great article - wcf manual way…the right way.
essentially, add service reference , svcutil lead client proxies become out of date on time; , fact solution has multiple types defined same class.
update: since writing reply have learnt not have answers in castle update below:
essentially, wcf manual way…the right way describes rather using add service reference, instead split wcf scheme separate dlls for:
contracts service implementation roll-your-own client proxiesboth service , client add together normal code references (not service references) contracts dll.
in way, service , client using same types (and not code-generated ones in client) , when contract changes - both service , client forced update less compile error appears. no more out-of-date clients.
wcf
No comments:
Post a Comment