Clik here to view.
AOP With castle–Part 3-The first interceptor
Previous Parts of the series Part 1 – The basic of interception Part 2 – Selecting Methods to intercept Usually the very first interceptor you can build with an AOP framework is the “logger...
View ArticleClik here to view.
Castle and Automock, avoid resolving properties
I use AutoMockingContainer extensively in my test projects, and I ‘ve build over time an automocking container that satisfy all of my needs. Thanks to Castle Windsor, using complex logic with the...
View ArticleClik here to view.
AoP with castle part 4–Adding AoP to service oriented App
Previous Parts of the series Part 1 – The basic of interception Part 2 – Selecting Methods to intercept Part 3 – The first interceptor AOP works great if you have clear interfaces where you want...
View ArticleManaging remote logging with Log4net and WCF
I’ve applications that can work in two distinct configuration, they are based on WPF and MVVM, where the VM communicates with the Domain / Business Logic through services like IXxxxService. All View...
View ArticleMoving between different IoC containers
I must admit that I always prefer castle Windsor over other IoC containers, but the main reason is that I’m really used to it and all its facilities. I know how to write facilities, and I know how it...
View ArticleMaking Castle and MEF happy togheter
If you use Mef to dynamically load handlers for your services (as described in this post), you will probably need to declare dependencies to various other software service. Since MEF is not born to...
View ArticleExposing WCF service without .svc extension
I know, this is a weird requirement, but sometimes they appear in your backlog. The story is: as company XXX I want to expose a service based on WCF in IIS without having the .svc suffix in the...
View Article