http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Hey, My point was to show that there is no need to write the second contract, like you did. I referenced you to generated code only for proof my concept; you don’t have to use it. BTW, if you don’t use the generated code and your contract is changed, how do you get the newer one for your client? http://ayende.com/3229/wcf-async-without-proxies#comment8http://ayende.com/3229/wcf-async-without-proxies#comment8Tue, 01 Apr 2008 21:26:27 GMTNati, The point here is to avoid having to generate a proxy http://ayende.com/3229/wcf-async-without-proxies#comment7http://ayende.com/3229/wcf-async-without-proxies#comment7Tue, 01 Apr 2008 21:14:09 GMTHello, Async pattern is a nice ability that WCF supplies but as far as I know the server doesn't have to know about the AsyncPattern you are using for your clients. Your code will work fine without the second contract. For your client you have to declare the AsyncPattern on your service contract mehods and when you implementing it you just have to call the standard Process method – WCF engine will do the rest for you. You can see implementation of this pattern by running svcutil.exe with your mex address and apply /async parameter on it. You will get fully generated proxy with async pattern implemented for each and every of your contract methods, while in the serve you don’t mention anything about it. http://ayende.com/3229/wcf-async-without-proxies#comment6http://ayende.com/3229/wcf-async-without-proxies#comment6Tue, 01 Apr 2008 21:05:18 GMTThat's my preference as well, although I'm not completely familarised with it yet. It's an interesting piece of code though. I like the approach. I HATE the generated proxies - they're such a p-i-t-a to manage, I find. http://ayende.com/3229/wcf-async-without-proxies#comment5http://ayende.com/3229/wcf-async-without-proxies#comment5Sun, 30 Mar 2008 21:09:20 GMTJohnny, Actually, I would probably use the Castle's WCF integration facility for this in real scenarios http://ayende.com/3229/wcf-async-without-proxies#comment4http://ayende.com/3229/wcf-async-without-proxies#comment4Sun, 30 Mar 2008 20:53:44 GMTHi. You might be interested in this alternative to using a proxy or a channel. http://www.acorns.com.au/blog/?p=113 http://ayende.com/3229/wcf-async-without-proxies#comment3http://ayende.com/3229/wcf-async-without-proxies#comment3Sun, 30 Mar 2008 20:36:24 GMTOutstanding, I'm going to go delete my proxy based code and refactor to this. http://ayende.com/3229/wcf-async-without-proxies#comment2http://ayende.com/3229/wcf-async-without-proxies#comment2Sat, 29 Mar 2008 16:28:38 GMTVery nice. I was completely unaware of this. http://ayende.com/3229/wcf-async-without-proxies#comment1http://ayende.com/3229/wcf-async-without-proxies#comment1Sat, 29 Mar 2008 14:54:38 GMT