c# - Applying AOP -


i've been using basic aop style solutions cross-cutting concerns security, logging, validation, etc. solution has envolved around castle windsor , dynamicproxy. i've gone down route because can apply using boo based dsl , keep code clean of attributes. told @ weekend have @ postsharp it's supposed "better" solution. i've had quick @ postsharp, i've been put off attribute usage.

has tried both solutions , care share experiences?

i looked @ castle-windsor short time (yet) can't comment on did use postsharp.

postsharp works weaving @ compile time. ads post-compile step build modifies code. code compiled if programmed cross cutting concerns code. bit more performant runtime weaving , because of use of attributes postsharp easy use. think using attributes aop isn't problematic using di. that's personal taste.

but...

if use castle dependency injection don't see reason why shouldn't use aop stuff. think though aop @ runtime bit slower @ compile time it's more powerful. aop , di in opinion related concepts think it's idea use 1 framework both. i'll @ castle stuff again next project need aop.


Comments

Popular posts from this blog

c++ - How do I get a multi line tooltip in MFC -

asp.net - In javascript how to find the height and width -

c# - DataTable to EnumerableRowCollection -