Dot Net EDI framework
A reader asked me a question, and I want to pass it along: “Do you know of any DOT NET frameworks for working with EDI?”
I didn’t, and a search of the web didn’t reveal anything that I could, in any confidence, recommend. So I bring this question to you. Do you know of a DOT NET framework that can be used for generating and or parsing EDI data? If you do, please comment below and let everyone know. I will also pass it on to my friend who is looking for this.
Development Frameworks
The reader that I mentioned asked about Dot Net, but there are other times and environments where companies need to setup and EDI interface for their implementation. I have spent most of my career working with enterprise level applications to handle the EDI transportation and transformation. But I have seen a few times when it would have been useful to code an interface for and EDI file onto a stand alone application. But I am not a developer in that sense. Hoping that some of you may be, what are some EDI frameworks or modules etc that you have used or know about? Java, C++, VB, or even perl, python, tcl, php, etc. Please leave a comment with the framework or tool that you know of. You can say a few words of eveluation if you can, or just leave a link to it and I will look them over and try to post about them over the next few weeks.
EDI and B2B tools
This brings up another point. I have been trying to add to my Toolbox page as I have gone along. I have posted a few tables and spreadsheets. I also had a post about tools that an effective integration engineer should use. I plan on posting more tools in my Toolbox too. And I have a reall love of free tools. But that is not the only kind of tool that I use, or will recomend. If you know of a tool or technology that you think others should know about, or might help them, post a link, or drop me a line and I will add it to my Toolbox or write a post about it. (or both)
So bring me your suggestions and I will share them with others and write an article about them when I can.
Thanks
Subscribe to "The Integration Engineer" by Email
Find out about the tools and services available at The Integration Engineer's Consulting site.
September 10th, 2009 at 12:37 pm
Roy,
we integrate with EDI feeds for large suppliers and we were unsuccesful in finding a suitable DOT NET framework.
We elected to ‘roll our own’ which has proven to be the best method in the long run.
Kind regards,
Ian Sweeney
CEO, billflo.com
September 11th, 2009 at 9:03 am
Ian,
Thanks for the feedback. It is kind of surprising that I haven’t found anything on this. Makes me wonder if Dot Net is just too cool for EDI, or if it is so easy to write your own EDI handler that no one has bothered making a framework for it?
Not a Dot Net developer myself, so I don’t know.
Roy
September 23rd, 2009 at 5:15 am
I thought Microsoft’s BizTalk provided enough EDI handling for most people?
I’m implementing an EDI solution in REALbasic, for a cross-platform client. Your EDI blog posts have been extremely helpful in clarifying some of the points where the vendor specs are ambiguous.
Thanks!
September 23rd, 2009 at 7:33 am
Andy,
I am really glad that you are finding my posts useful. If you have any more ambiguity that is causing you grief I would be happy to help, just let me know what you are looking at.
I hadn’t looked at BizTalk. From my brief evaluation of it years ago, it is more than just a framework, but an Enterprise level application.
Have you used BizTalk as something that you can embed into an app? My understanding was that BizTalk was its own EAI, but that is an impression from years ago and I may have miss-remembered.
October 1st, 2010 at 7:47 am
Has anyone tried the DotNetEDI library that can be found here: “http://sites.google.com/site/dotnetedi/”. If so, is it useful or any good?
Thanks,
-Jeff
October 27th, 2010 at 1:08 pm
There does not appear to be a trial of this product. They only show a few lines of example code. Also, it is not clear whether this is also used for parsing EDI (or just creating new EDI files).
We use EDIDEV and it suits most of our needs. It works with .NET, but the code is still very procedure oriented (at least the VB.NET version). Although it uses .NET, it uses Interop.