The main reason for including WCF is because of the nice integration between it and the Windsor IoC. Being able to write IoC components and then just expose them as services with a bit of config is a very nice story.
Notepad, thoughts out loud, learning in public, misunderstandings, mistakes. undiluted opinions. I'm Mike Hadlow, an itinerant developer. I live (and try to work in) Brighton on the south coast of England. Please don't mistake me for an expert in anything. I love technology and programming, but make no claims to be any good at it. Much of what you read here may be poorly thought out, wrong, or just plain dangerous.
Posts
7 comments:
nice, but what's so great about WCF? my one brush with it so far was a traumatic episode of bloody-minded YAGNI violation...
Jon, very good!
The main reason for including WCF is because of the nice integration between it and the Windsor IoC. Being able to write IoC components and then just expose them as services with a bit of config is a very nice story.
sounds really interesting - i use windsor a lot. can you point me to any examples (or elaborate a tiny bit)?
It's another product of Ayende's planet sized brain (but I don't think anyone's ever asked him to look after a carpark):
http://www.ayende.com/Blog/archive/2007/06/12/WCF-Windsor-Integration.aspx
I've got a vague plan to do a detailed post on the subject soonish, so watch this space :)
cool, thanks. ayende gives great open source but i find the signal/noise ratio on his blog a bit rubbish - i sometimes miss the gems!
yo Mike - great post.
imo this is all stuff that Mainstream.NET people should do anyway ...
I mean - High cohesion/Low coupling? that's software engineering 101
Grammar: "Less bugs" should be "Fewer bugs"
Post a Comment