Living in the Tech Avalanche Generation

If I had a Fluent Interface for WCF Configuration I would…..

March 15th, 2009 | Category: WCF

It would look something like this I guess:

var config = Wcf.Configure
                .AddressAt(“net.tcp://localhost:9002/myservice”)
                .TransportOn(Transports.Tcp)
                .SecureFor(SecurityMode.None)
                .etc
                .etc

I think this gets idea over? I have at least one volunteer (bravo Mark) and so Hi Ho Hi Ho it’s off to work we go.

6 Comments so far

Peter Bromberg March 16th, 2009 10:33 am

A capital idea. WCF configuration files be damned!
Simon Segal March 16th, 2009 11:00 am

Peter

My friend Mark and I are going to start out with this. For my part, it’s down low in my queue of things to knock out, so we are planning on getting the most basic scenarios catered for. The typical SME intranet / LAN application scenarios and with little concern for the security aspect. Neither of us are deep believers in the WCF security model or rather it’s way of doing things and so we are not going to put it up high on the list requirements for the moment.
Roberto Hernandez March 19th, 2009 12:44 pm

Sounds like a great project, if you need additional volunteers send me an email. I would love to get my hands dirty on this.

Roberto.-
Kang The Koder » Blog Archive » Introducing Fluent WCF March 31st, 2009 11:20 am

[...] 2 weeks ago Simon and I started to work on building a fluent interface to configure WCF. Our main aim in doing so is to cover the the scenarios of configuring Services and Clients 80% (or [...]
Sandy July 8th, 2009 1:22 pm

I am sure you have seen this but I thought I would pass it on. David Kirkland has written a library that has a WCF Fluent interface. You can download the source at:

http://code.google.com/p/vitamink/
Simon Segal July 8th, 2009 7:40 pm

Sandy

I hadn’t seen it but will check it out. I am not using WCF much these days unless I have to punch a hole through the firewall but it’s (config) is still a pain.

All messaging I do currently (behind the firewall) is being built using nServiceBus.

Thanks for pointing it out and I will definitely be checking it out.