Current design problems with PostSharp code weavers

by Gael Fraiteur on 15 Jan 2007

As I wrote two posts ago, I discovered some design problems with both PostSharp aspect weavers: the low-level one and Laos, the high-level one.

Subscribe to our newsletter for release news and a monthly status report.

You can unsubscribe at any time.

I have written a log of improvement proposals in the PostSharp Roadmap:

#28: Low-level code weaver: better support for multiple catch/finally advices. (G. Fraiteur)
#29: Low-level code weaver: support for typed catches (G. Fraiteur)
#30: Low-level code weaver: new join point Before/After/InsteadOf Load Field Address (G. Fraiteur)
#31: Laos: to ignore exceptions (O. Conijn, G. Fraiteur)
#32: Multicasting of custom attributes: complete overwriting (not partial any more) (G. Fraiteur)

Since most are breaking changes, I would like to implement them before Beta 1. I know some users already rely on these features. That's why I invite them to send feedback to share their opinion. Please use the add comment feature of the website for this (not this blog post).

Thank you.

Gael