|
今天把Net AOP Frameworks Research Report v1.1一文中列出的.Net下的AOP实现方案的源码都过了一遍，每看一个方案的自我介绍，首先印入眼帘的往往就是其功能定位
1. Aspect#
在所有的方案中，不谈技术能力的高低，只从其定位和文档质量来说
首先，它的定位非常明确，也因此他能够被castle项目收录为子
当然，从技术的角度来讲，dynamicproxy一点也不先进
还有就是它的文档质量和示例代码非常简单易懂，他的two minute tutorial确实做到了two minute就会使用，这个也是值得其他AOP方案大大学习的地方。
2. AspectDNG
AspectDNG和Aspect#其实有一点是非常相似的
不过，AspectDNG的文档可就比Aspect#差了点
评论 以上两者是现有的.NET下的AOP实现的佼佼者，分别是两个很明确的思路，都很好的利用了现有的第三方类库作为基础
值得思索的是，其他的方案都没有这两个方案成功，不仅仅是因为其他
从底层技术的角度讲，主流的AOP Framework一般有如下三种织入方式：
1、基于dynamicproxy的运行时interceptio
2、基于IL级别的静态织入；
3、基于IL级别的动态载入时织入；
从Configuratuion方式的角度讲，主流的AOP Framework一般有如下四种配置方式：
1、类似Aspect#的独立的自定义Configuration
2、类似AspectDNG的，基于XML的Configura
3、基于Custom Attribute的Configuration格式；
4、类似AspectJ的特定语言扩展及相应的Compiler；
1. Aspect#Version: Link: http://aspectsharp.sourceforge.net/ Status: beta Dependency: antlr, Castle.DynamicProxy Description: Aspect# is an AOP (Aspect Oriented Programming) framework for the CLI (.Net and Mono). It relies on DynamicProxy and offers a built-in language to declare and configure aspects, and is compliant to AopAlliance. It became part of the Castle Project in June 2005. - Custom mini configuration language, not xml. - Mix/Intercept classes and methods through dicnamic proxy approach. Restrictions: - Classes to be created dynamic proxy for shouldn’t be sealed and only virtual methods can be intercepted. - Using intercepted classes is not completely transaparent to users that users should explicit create the dynamically proxied class through the AspectEngine. - No static weaving support. 2. AspectDNGVersion: 0.7 Status: beta Link: http://www.dotnetguru.org/downloads/AspectDNG/??? Dependency: mono.petoolkit, rail Description: AspectDNG is a .NET aspect weaver, that's to say a tool that can "transplant" code into an existing assembly. This transplant is made after the standard .NET compilation, which means that both aspect and the so called "base" code (the one the transplant will be operated on) can be developped in any programming language that is compatible with .NET CLS. Another way to say that: AspectDNG works on assemblies (EXE or DLL) that may have been created out of C#, VB.NET, Eiffel.NET, Mananged C++... - Xml, Xpath based configuration file format. - IL level static Weaving. - Custom xml based disassembled language ILML which can be used to convert assemblies to and be modified/combined and then converted to assemblies. Restrictions: - Static weaving only. - Not very stable. Version: Link: http://www.cs.virginia.edu/~eos Status: beta Dependency: none Description: Eos is an aspect-oriented extension for C# on Microsoft® .NET Framework™. Eos aims to improve upon the current aspect-oriented language model in three dimensions. First, it generalizes aspect instantiation & advice weaving model to eliminate the need for the work-arounds that are unavoidable today when aspects are used to express certain crosscutting concerns. Second it generalizes the join point model. Third it aims to eliminate the distinction between class and aspect constructs in favor of a single conceptual building block that combines the expressive capabilities of current classes and aspects, significantly improving conceptual integrity and uniformity in language design. The language is very similar to AspectJ except for constructs which are not implemented in Eos and constructs which AspectJ does not provides. - AspectJ like extended C# langauage and custom compiler. Restrictions: - Static weaving only. - Not very stable. Version: 0.7 Link: http://theagiledeveloper.com/category/15.aspx Status: beta Dependency: none Description: Encase is an aspect oriented programming framework for the .NET Platform written in C#. Encase is unique in that it provides aspects to be applied during runtime in managed code rather then being configuration file based that other AOP frameworks rely upon. The advantage of applying aspects in this way is that it promotes productivity to developers new and/or unfamiliar with AOP. Restrictions: - Encase cannot mixin multiple classes that implement a shared interface? For instance, if class A implements Ialphabet, and class B implements Ialphabet, classes A and B can not both be mixed in as an aspect. - Encase can only provide interception and aspect weaving to virtual (overriable) methods and properties. - Encase is unable to apply aspects to sealed (NotInheritable) classes. - Like Aspect#, but more unstable. Version: Link: http://gael.fraiteur.net/postsharp.aspx Status: alpha Dependency: none Description: PostSharp is a free and open-source post-compiler for the .NET Framework. PostSharp is an extensible platform that makes it easy to develop and execute static program analysis and program transformation plug-ins. - Developped under .Net Framework 2.0 beta - There is a very good third pary collection library – “Xipho.Collections” for .Net 2.0 in the source code Restrictions: - Not say to be a really aop framework yet. Version: Dependency: none Description: The LOOM .NET project aims to investigate and promote the usage of AOP in the context of the Microsoft .NET framework. We have been developing two AOP tools (so called weavers) that all implement different approaches to weaving: A runtime weaver crating weaved objects on the fly and a static weaver. Main - Support under .Net Framework 2.0 beta - Include both dynamic proxy based dynamic interception and il level rail like static weaving support. Restrictions: - Not very stable. 7. Others AspectC# (AspectJ like C# extended compiler)
Weave.NET (provide a load
|
