I took the last opportunity to change the public interface of PostSharp Laos. Hopefully, for most of you, the changes will be trivial and a find-and-replace will do the job.
The old design was to pass a lot of parameter to each method like
Last week, Wang posted a very relevant remark: the integration of PostSharp in the build process of Visual Basic .NET projects simply did not work.
The reason was simple: the integration was based on "compilation symbols" (or constants)
If you develop low-level transformations you would surely syntax coloring for MSIL. I have finally written a User Highlighter for the great editor PSPad (this editor is brewed in the same town as the famous Pilsner Urquel, btw).
The filter
I've just put online a flash tutorial that shows how to create a Trace aspect using PostSharp Laos. I know, people that read my blog probably already master this trivial example...
Comments are welcome. A question I ask to myself is: what is
I have written that the newly redesigned Code Weaver now support type-level advices (well, to be precise, type-level join points). The first implementation is the new AggregationAspect
in PostSharp Laos.
So what's aggregation?
Say you
The ones who already use the Code Weaver will maybe get angry but that's something I needed to do before going beta: I have redesigned quite deeply the low-level code weaver. Most changes are documented in the CHANGELOG.txt file.
So what has