Tag Archives: AOP

Retrying with .net WebAPI client

We’ve been building a prototype Windows 8 dashboard to show management information on our Azure application. One thing we were conscious of was unreliable mobile network connections so we wanted to make some attempt to retry if we get a … Continue reading

Posted in Uncategorized | Tagged , , | Leave a comment

Caching with Entity Framework

As I said before in my post about the repository pattern, entity framework doesn’t come with any caching.  I’m pretty sure this will be added at some point, and I look forward to not worrying about it myself…  After all, … Continue reading

Posted in Uncategorized | Tagged , , , | Leave a comment

Caching Aspect

Following on from logging, the other aspect we’re using is caching.  Goal is similar, make it really easy to cache but not litter the code with lots of calls to caches (or worse, random static dictionaries hidden in classes).  The … Continue reading

Posted in Uncategorized | Tagged , , | 2 Comments

Logging Aspect

In a previous post I talked about my approach to Aspect Oriented Programming (AOP) in Castle Windsor.  In this one I’m going to chat a bit about how I used this for logging. My goal is simple:  I want to … Continue reading

Posted in Uncategorized | Tagged , | 1 Comment

Implications of Proxy classes

I said in a previous post about there being some things to watch out for when using proxies…  Here’s what I’ve seen, there’s probably more, add your experiences to the comments 🙂 This is really only an issue if you … Continue reading

Posted in Uncategorized | Tagged , | 2 Comments

Aspect Oriented Programming with Castle Windsor

Aspect Oriented Programming (AOP) is a way of addressing the ‘cross cutting concerns’ of a system – e.g. logging, security, transactions, caching etc.  Using aspects you can apply these concerns without hand writing it into each place you need it.  … Continue reading

Posted in Uncategorized | Tagged , | 1 Comment