Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>So far AOP is tied to frameworks, so you should read the documentation of the AOP framework rather then general approach.</p> <p>But we can specify three common types of AOP:</p> <ol> <li>pre code injection (in the code file) [code generators that work pior the pre compilation]</li> <li>runtime code injection (inject, swamp pointers, in memory) [spring?, my own framework]</li> <li>post code injection [postSharp]</li> </ol> <p>most resources can be found here: "<a href="http://csharp-source.net/open-source/aspect-oriented-frameworks" rel="nofollow">http://csharp-source.net/open-source/aspect-oriented-frameworks</a>"</p> <p>The most common use is a plugin architecture, logging, caching as well as some domain specific AOP like setting some specific properties on a object that is in a certain domain and state from AOP so that the dev doesn't care about it, other than that presistance layers can use AOP to generate SQL command objects etc.</p> <p>The thing in AOP is that you need to have a good understanding how the system works if you want to go beyond the common things like Logging, many junior devs don't get AOP so I would be careful with using it in a domain specific way, this will work fine if you are in a strong dev team that has lots of experience with AOP.</p> <p>EDIT: Here is an good <a href="http://www.springframework.net/doc/reference/html/aop-quickstart.html" rel="nofollow">tutorial</a> to spring AOP, Spring is a huge beast, but once you learn it it works very well, the only downside is xml configuration rather then fluent one.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload