Not sure where you're at in your progress, but in our processing of 834/835 files, we use home-grown parser apps to break the files down into more of a flat-file layout, which makes them easier for actual data processing (they're each slightly modified/tweaked from the x12 specs in order to be better used from what our partners send us and for what our business needs are).
Using them in conjunction with SSIS, I'm passing raw EDI files through the parser via a ExecProcess task, and then using the resulting flat file in the data flows. Some raw files do end up needing a little pre-parsing using some regex in a script component, but it at least gets the job done. Again, this is nice if you already have some stand-alone parsing apps.
Of course, with the upcoming 5010 transaction set (to be implemented by 1/1/12), we'll be taking a fresh look at how we handle these files ... it'd be nice to eventually work our parsing logic into a custom component without a 3rd-party product, but I think that'll be a warm weather project 🙂
(I'll keep my eyes on this thread ...) 😀