Eric Bodden » Aspect-oriented approaches targeting the .NET Fram. Introduction This is an incomplete list of frameworks and tools supporting aspect-oriented programming under the .NET framework. It is separated by technology. The comments stated below are sometimes just copied form the author’s website, to those are not necessarily objective evaluations! If you find anything is missing or this site could be improved in any other way, please sent your comment to Eric Bodden. You can find our related (German) article here: Torsten Weber und Eric Bodden – bit-Fabrik: Zweigstelle, Hauptstelle, Dienstleister: Aspektorientierte Programmierung mit .NET. Proxy-based approaches Aspect# Project URL: Aspect# is an AOP (Aspect Oriented Programming) framework for the CLI (.Net and Mono). Encase AOP Project URL: Encase is an aspect oriented programming framework for the .NET Platform written in C#. Puzzle Framework Project URL: The Orthogonal Weaving Model. Log4PostSharp - AOP and logging. Free source code and programmin.
Introduction Log files are crucial when it comes to troubleshooting an application or finding the exact source of a bug. Unfortunately, the more information the application logs, the more its code gets cluttered with logging statements. Readability of source code decreases and, in a team of developers, it may be hard to keep consistency of logged data. If these problems sound familiar to you, Log4PostSharp is for you. It inserts logging statements without touching your source code. It injects calls to log4net methods into the DLL and EXE files automatically, right after they are compiled.
This guarantees consistency of log files, and allows you to forget about logging at all. Quick comparison To illustrate the difference Log4PostSharp makes, this section compares two snippets of code. In the first snippet, the logging has been added in the traditional way: This is where Log4PostSharp comes to rescue. [Log] public void Save() { Configuration.Save(); } Demo How does it work? Customization. Rating of Open Source AOP Frameworks in .Net. Free source code a. Introduction In the days where business agility is becoming the definite need of any business / IT infrastructure, quite frequently we are ending up with facing scenarios where we need to develop applications that are flexible and easily manageable.
The flexibility in an application’s architecture is demanded by the emerging business competitions, pressure to sustain the challenges created by the innovative business models, need to sustain the growing customer’s base of an established business, etc. Say for example you are building an e-commerce system with an innovative business model, targeting a niche market. Soon, it is becoming hot in the market and your system is witnessing a rapidly growing user base, in a short span of time. The system starts crawling, failing to sustain the increased user load there by creating significant loss to your business and to the goodwill you have created with your hard work and innovation. Situations that may pull your business down may be like: 7 Approaches for AOP in .Net. Aspects of Domain Model Management.
Introduction As can be learned from books such as Domain Driven Design [Evans DDD] and Applying Domain Driven Design and Patterns [Nilsson ADDDP], introducing the Domain Model pattern (Patterns of Enterprise Application Architecture [Fowler PoEAA]) into your application architecture may promise many benefits, but they do not come for free. Using a domain model is rarely as easy as just creating the actual domain model classes and then using them. Soon enough one discovers that sizable amounts of infrastructure code will also be required in support of the domain model. Prominent among the infrastructure demands that accompany a domain model is of course persistence - normally to a relational database. Where Do We Put Our Infrastructure Code? As the amount of infrastructure code grows, finding a good architecture for dealing with it all becomes increasingly important. Time to Refactor Unfortunately, the trade-off offered here might not be good enough to last you in the long run.
Figure 1. Using the Policy Injection Application Block in ASP.NET. Ne technique becoming increasingly popular with developers is the adoption of an Aspect-Oriented Programming (AOP) model. AOP provides techniques for changing the behavior of business objects and other classes through the application of policies, making it easier to implement common crosscutting concerns such as logging, validation, exception handling, caching, and more. The terminology of AOP uses the word "concern" to mean a task or feature of an application. Core concerns are the features usually unique to a class or object, such as extracting specific data from a database, or calculating the result of a function directly applicable to the class or object. Tasks common to more than one class or object are crosscutting concerns. Policy injection provides one approach to simplifying and unifying the implementation of crosscutting concerns. The Policy Injection Application Block is highly flexible and extensible.
Aspect-oriented approaches using the .NET Framework.