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 Models depends from one or more services and thanks to Castle I can decide with configuration file which concrete class to use for [...]
Continue reading about Managing remote logging with Log4net and WCF
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 to put some standard and shared logic, and a Service Oriented Application falls in this category. A service is [...]
Continue reading about AoP with castle part 4–Adding AoP to service oriented App
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 AutomockingContainer is a breeze. Suppose you have this ViewModel Figure 1: ViewModel under test The only aspect I’m interested in is the SelectedLinkResult [...]
Continue reading about Castle and Automock, avoid resolving properties
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 Interceptorâ€, because it is simple and useful, especially when you expose some services with WPF. Consider this scenario: you expose some [...]
Continue reading about AOP With castle–Part 3-The first interceptor
I have a little application that has a custom MVP pattern implemented in Winform. Instead of using configuration file to register all the View (implemented by windows Forms) I decided to move towards fluent configuration to use a “convention over configurationâ€. My convention is that all View lives in a specific namespace, and you can [...]
Continue reading about Castle, MVC, and verify Fluent Registration