﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>akhtar khan commented on WCF, Mocking and IoC: Oh MY!</title><description>nice place to get knoledge
</description><link>http://ayende.com/2095/wcf-mocking-and-ioc-oh-my#comment9</link><guid>http://ayende.com/2095/wcf-mocking-and-ioc-oh-my#comment9</guid><pubDate>Thu, 29 Mar 2007 10:33:59 GMT</pubDate></item><item><title>Insert Catchy Title Here commented on WCF, Mocking and IoC: Oh MY!</title><description>Mocking Windows Communication Foundation (WCF)
</description><link>http://ayende.com/2095/wcf-mocking-and-ioc-oh-my#comment8</link><guid>http://ayende.com/2095/wcf-mocking-and-ioc-oh-my#comment8</guid><pubDate>Sun, 11 Feb 2007 20:06:49 GMT</pubDate></item><item><title>Tomas Restrepo commented on WCF, Mocking and IoC: Oh MY!</title><description>I understood that, Oren, I just don't see what exactly is it that you're gaining by that after going through all that trouble. Maybe I just prefer to keep things simpler unless there is something definite and clear that absolutely wins me something, or, most likely, it's just me being thickheaded today. 
</description><link>http://ayende.com/2095/wcf-mocking-and-ioc-oh-my#comment7</link><guid>http://ayende.com/2095/wcf-mocking-and-ioc-oh-my#comment7</guid><pubDate>Sun, 11 Feb 2007 19:40:30 GMT</pubDate></item><item><title>Ayende Rahien commented on WCF, Mocking and IoC: Oh MY!</title><description>Think about the real application.
  
My components are getting their WCF services from Windsor.
  
When I need to do integration tests, they are still getting them from Windsor. And the instances that they get are not mocked.
  
What is mocked in this case is the implementation of the service that is running on the other side of WCF.
  
I am not going through Windsor to get the mocked instance, I am working directly with WCF to mock the service instance.
</description><link>http://ayende.com/2095/wcf-mocking-and-ioc-oh-my#comment6</link><guid>http://ayende.com/2095/wcf-mocking-and-ioc-oh-my#comment6</guid><pubDate>Sun, 11 Feb 2007 19:25:06 GMT</pubDate></item><item><title>Tomas Restrepo commented on WCF, Mocking and IoC: Oh MY!</title><description>I get wanting to run the service inside WCF for integration tests. I've done that very successfully before and I agree it's a great idea. What maybe confused me was the reference to mocking. 
  
To put it this way: Mocking the service interface? great! extending windsor to allow it to instantiate WCF service proxies? Great! Going through Windsor and WCF to get to a mocked service instance? hummm... not sure exactly the benefit of it here.
</description><link>http://ayende.com/2095/wcf-mocking-and-ioc-oh-my#comment5</link><guid>http://ayende.com/2095/wcf-mocking-and-ioc-oh-my#comment5</guid><pubDate>Sun, 11 Feb 2007 14:55:12 GMT</pubDate></item><item><title>Ayende Rahien commented on WCF, Mocking and IoC: Oh MY!</title><description>This is actually more than just about mocking WCF.
  
It is about integrating a WCF service directly into the application, in a way that is mostly transparent to my application.
  
This means that I can get a WCF service from the container without needing to worry about anything else that it might need.
  
I probably should have broken the post into several posts, but I was on a role and couldn't face the attempt to split it into standalone logical units.
  
  
A story from the real world:
  
I once had a web service client that would start consume 100% CPU for a long time, if and only if it pulled over 500 messages in a span of three minutes. Trying to reproduce that without using the real service failed, eventually I managed to track the problem down to the way accepting such a large load of messages would strain the database, which would kick off the system's auto recovery mode, which...
  
  
This is something that you are only ever going to find out when you are doing integration tests, and when that is the case, I really want to be able to test in this scenario, which include testing through the WCF pipeline itself.
</description><link>http://ayende.com/2095/wcf-mocking-and-ioc-oh-my#comment4</link><guid>http://ayende.com/2095/wcf-mocking-and-ioc-oh-my#comment4</guid><pubDate>Sun, 11 Feb 2007 05:18:14 GMT</pubDate></item><item><title>Ayende Rahien commented on WCF, Mocking and IoC: Oh MY!</title><description>Unbelievable,
  
someone actually read it to the end :-)
  
I actually do sleep, monday 10AM - 11AM, ever other week :-)
  
</description><link>http://ayende.com/2095/wcf-mocking-and-ioc-oh-my#comment3</link><guid>http://ayende.com/2095/wcf-mocking-and-ioc-oh-my#comment3</guid><pubDate>Sun, 11 Feb 2007 05:02:12 GMT</pubDate></item><item><title>Tomas Restrepo commented on WCF, Mocking and IoC: Oh MY!</title><description>Pretty cool, and pretty nifty, but I'm not sure if it's really worth it to add all that complexity around just to add the test. Maybe I'm missing something, but just how much value do you get over simply mocking the service interface on the client side locally and leaving the WCF code out of the picture completely?
</description><link>http://ayende.com/2095/wcf-mocking-and-ioc-oh-my#comment2</link><guid>http://ayende.com/2095/wcf-mocking-and-ioc-oh-my#comment2</guid><pubDate>Sun, 11 Feb 2007 03:42:59 GMT</pubDate></item><item><title>Jay R. Wren commented on WCF, Mocking and IoC: Oh MY!</title><description>AMAZING WORK!
  
  
I call this the prevailing WCF real-world blog post on the internet right now.
  
  
Do you sleep?
</description><link>http://ayende.com/2095/wcf-mocking-and-ioc-oh-my#comment1</link><guid>http://ayende.com/2095/wcf-mocking-and-ioc-oh-my#comment1</guid><pubDate>Sat, 10 Feb 2007 22:39:13 GMT</pubDate></item></channel></rss>