1. Aspect-Oriented Programming: The Good, the Bad, the Ugly and the Hope John Lam Naleco Research Inc. http://www.iunknown.com

4. The view from 35,000 feet

5. Monolithic programs

6. Modular programming

7. Object-oriented programming

8. AOP: Identifying cross-cuts

9. AOP: Defining aspects

10. AOP: Weaving aspects

11. The view from 5,000 feet

12. Monolithic programs

20. Modular programming

25. Object-oriented programming

27. OOP: .NET Frameworks System.Object System.Web.UI.Control WebControl Button Repeater CheckBox HyperLink Image AdRotator Calendar ValidationSummary System.Web.UI.WebControls Namespace Label LinkButton Panel RadioButton ImageButton Table BaseDataList DataList DataGrid ListControl CheckBoxList DropDownList ListBox RadioButtonList BaseValidator CompareValidator CustomValidator RangeValidator RegularExpressionValidator RequiredFieldValidator TableCell TableRow TextBox TableHeaderCell

29. AOP: Identifying cross-cuts

30. AOP: Defining aspects

31. AOP: Weaving aspects

33. The view from 50 feet

34. The Good: AOP solves problems Public Function ReadEmployeeSalary( id as Integer ) as Single Trace.WriteLine( String.Format( "Reading employee # {0}'s salary", id ) ) If System.Threading.Thread.CurrentPrincipal.IsInRole( "manager" ) Then Try ' Code that reads employee's salary Catch e as FatalException Logging.LogFatalException( e, "ReadEmployeeSalary" ) End Try End If End Sub

36. Aspects can implement policies Public Function ReadEmployeeSalary( id as Integer ) as Single Trace.WriteLine( String.Format( "Reading employee # {0}'s salary", id ) ) If System.Threading.Thread.CurrentPrincipal.IsInRole( "manager" ) Then Try ' Code that reads employee's salary Catch e as FatalException Logging.LogFatalException( e, "ReadEmployeeSalary" ) End Try End If End Sub 1 2 3

37. Aspects can implement policies public class SecurityPolicy { public bool AccessCheck() { return System.Threading.Thread.CurrentPrincipal.IsInRole( "manager" ); } } public class TracingPolicy { public void Before( CallContext c ) { Trace.WriteLine( String.Format( "Called: {0}", c.MethodName ) ); } } public class ExceptionPolicy { public void Thrown( FatalException e ) { Logger.LogFatalException( e ); } } 1 2 3

38. Weaving aspects before methods public class TracingPolicy { public void Before( CallContext c ) { Trace.WriteLine( String.Format( &quot;Called: {0}&quot;, c.MethodName ) ); } } <weave> <aspect target=&quot;public *.*::*( * )&quot; type=&quot;Before&quot; method=&quot;TracingPolicy.Before( CallContext )&quot;/> </weave>

39. Weaving aspects around methods public class SecurityPolicy { public bool AccessCheck() { return System.Threading.Thread.CurrentPrincipal.IsInRole( &quot;manager&quot; ); } } <weave> <aspect target=&quot; [ interface:ManagerOnly == true ] public *.*::*( * )&quot; type=&quot;Around&quot; method=&quot;SecurityPolicy.AccessCheck()&quot;/> </weave> [ ManagerOnly ] public interface ISensitiveEmployeeData { float ReadEmployeeSalary( int id ); ... }

40. Weaving aspects around methods public class ExceptionPolicy { public void Thrown( FatalException e ) { Logger.LogFatalException( e ); } } <weave> <aspect target=&quot;public *.*::*( * )&quot; type=&quot;Thrown( FatalException )&quot; method=&quot;ExceptionPolicy.Thrown( FatalException )&quot;/> </weave>