Your SlideShare is downloading. ×
Aspect oriented programming in .Net
Aspect oriented programming in .Net
Aspect oriented programming in .Net
Aspect oriented programming in .Net
Aspect oriented programming in .Net
Aspect oriented programming in .Net
Aspect oriented programming in .Net
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Aspect oriented programming in .Net

698

Published on

AOP programming in .Net using PostSharp

AOP programming in .Net using PostSharp

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
698
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Aspect Oriented Programming in .Net with PostSharp Paul Fryer Software Architect, Fiserv
  • 2. Agenda
    • What is AOP?
    • What is PostSharp for .net?
    • What’s the value?
    • Common Aspects
    • Demo
  • 3. What is AOP?
    • Wikipedia says: In computing, aspect-oriented programming (AOP) is a programming paradigm which aims to increase modularity by allowing the separation of cross-cutting concerns.
  • 4. What is PostSharp for .Net?
    • PostSharp is a .net framework for aspect management.
    • PostSharp injects aspects in a post built step.
    • This method is known as “static weaving” or “IL weaving” because it literally rewrites your IL code after the compilation of source.
  • 5. What’s the value?
    • Cleaner source code
      • Easier to understand
      • Easier to refactor/manage
      • Easier to onboard junior developers
    • Less source code
      • 15% less code
    • Less coupling
      • 20% less coupling
  • 6. Common Aspects
    • These are all potential cross cutting concerns:
      • Logging
      • Exception Handling
      • Validation
      • Caching
      • Multithreading
      • Transactions
      • Auditing
  • 7. DEMO TIME
    • http://aopdemo.codeplex.com/

×