Geeks With Blogs
Random Musing Putting it together one piece at a time...

There're some difference between Indigo and WCF which I'll highlight here.

1. WsProfileBinding is not longer there
wsProfileBinding is a secure, reliable and interoperable binding based on WS-Reliable Messsaging and used for one-way service contracts. Basically it's fire and forget. The current downloadable WCF installation no longer uses wsProfileBinding, instead you should use wsHttpBinding to replace that and use Reliable Session to configure that in the config file to enable reliable messanging

2. ServiceHost can no longer be used with typed arguments
If you want to host your services in an application, you can no longer use the ServiceHost class with type arguments will no longer work. For example

Indigo:
using (ServiceHost<myService> myHost = new ServiceHost<myService>())

WCF:
ServiceHost myHost = new ServiceHost(typeof(myService))

Similary, when creating proxies and ChannelFactories, there're some minute differences to take note as well

Indigo
ISample proxy = ChannelFactory.CreateChannel<ISample>(myURI, myBinding)

WCF
ISample proxy = ChannelFactory<ISample>.CreateChannel(uri, endpointaddress);

3. Some changes in Method names
There're some small changes within ServiceHost, but they should be self explanatory enough. For example,

Indigo
AddEndpoint  

WCF:
AddServiceEndpoint

Interface name changes
Indigo:
IChannel

WCF:
IClientChannel

Posted on Friday, December 22, 2006 2:31 PM BPM , .Net , Architecture , Connected Systems | Back to top


Comments on this post: Some differences between Indigo and WCF

No comments posted yet.
Your comment:
 (will show your gravatar)


Copyright © Nestor | Powered by: GeeksWithBlogs.net