Tomas Restrepo writes:

While useful, I’m not quite sure if it’s actually needed at all. The reason is that IBlogExtension itself lends very nicely to stacking, so it’s fairly easy to introduce preprocessors by simply stacking them up. Heck, I could easily modify my own to make it usable with any IBlogExtension by adding a simple extra configuration dialog.

Im not completely sold on this. I believe that the IBlogExtension and the preprocessing need to be separated. When they are separated, then you’ve achieved code reuse.

For example, if the Outlook HTML preprocessor is implemented in a manner described in my earlier post, then the preprocessor can also plug into another IBlogExtension without writing any new code. Simply drop the assembly in place, and any IBlogExtension using the described architecture can take advantage of the preprocessing features.

Maybe it is too early for this discussion, but we should still keep something like this in mind…