Another problem I faced while working on BRE recently.
If you call BRE from orchestration using Call BRE shape and pass in the message into it, the message lose all its context and you cannot access it after it. It seems Call BRE shape creates new message out of the passed XLangMessage and points the same message variable to it.
Solution: Just extract all values from the context before you make a call to BRE.
SSIS 2005
Flat File Connection Manager Bug-
I was bit shocked to see this bug which MS is still reluctant to fix.
If you change the "data rows to skip" settings under "Preview" tab it will impact how the rows are imported actually using a file and is not just confined to the preview of the data in that window. Essentially, if you set it to say 100, the package when executed will skip 100 rows from the file and guess what not just from beginning but also also the random positions as well.
If MS says this is a minor UI bug then the question is why is it skipping rows from the random positions also and not just from the top?? I am sure no developer will like to skip random rows from the file :)
It is a BUG indeed.