A few days ago I released a new version of the BRE Pipeline Framework  with a few improvements.  Below are a couple of features I am thinking of for the next version of the framework which I am targeting for a May/June release.

  • Thus far every time you use the BRE Pipeline Framework pipeline component you must create and use an InstructionLoader BRE Policy (see the codeplex project page if you want to read more about this) to choose which MetaInstruction plugins you want to instantiate, including the out of the box MetaInstructions.  I am now planning on having the out of the box MetaInstructions automatically instantiated without the use of an InstructionLoader Policy which will now only be necessary if you want to make use of your own custom MetaInstruction plugins.  As the out of the box MetaInstructions cater for a large range of scenarios this should reduce the amount of development and maintenance that is required to use the component while preserving its extensibility.
  • Add methods/vocabulary definitions to the out of the box MetaInstructions that will allow you to perform party resolution, resolving the DestinationPartyName context property based on identifiers set up against configured parties (somewhat similar to what’s described in this MSDN post).
  • Add methods/vocabulary definitions to the out of the box MetaInstructions that allow you to set message part context properties against either the body part or any other part by index.  This would be handy to set properties such as attachment file names in SMTP message parts etc…
  • Add methods/vocabulary definitions to the out of the box MetaInstructions that allow you to modify namespaces, elements, attributes and XML declarations in XML messages using the capabilities of the XMLTranslatorStream class (see this detailed blog post by my colleague Mahindra Morar for more details on usage of this class).  I have previously blogged on using the XMLTranslatorStream in custom MetaInstructions to manipulate namespaces using the BRE Pipeline Framework but I think that some of the key capabilities of the XMLTranslatorStream class should be catered for in the out of the box MetaInstructions.

Please let me know if you have any other suggestions and ideas regarding the future of the BRE Pipeline Framework.