AOP and Debuggability

I'll be giving a short presentation at an upcoming Microsoft workshop on Aspect Oriented Programming on .NET. More information about the workshop is here:  https://research.microsoft.com/workshops/aop/

I don't know much about AOP, but I do know a thing or two about debugging infrastructure, and that's what I'll be talking about.

The basic idea behind AOP is that you take an input assembly, and then morph it on the fly. That morphing may be idempotent instrumentation, or it may be more complex like adding methods to an existing class. You'll want to be able to debug your final result once you make these changes.

The key things I'll be discussing will include:
- debuggability of different CLR technologies for rewriting.
- restrictions on the PDBs.
- split between platform API and the debugger application.

I'll post back here with whatever I present.
[update: 11/14/05] Presentation is now available here: https://blogs.msdn.com/jmstall/archive/2005/11/15/aop_presentation_2.aspx