Create EDI Documents with .NET


With the DotNetEDI library you can quickly build any kind of EDI document using C# and VB.NET.

Only $499 

 

Money Back Guarantee 
If you don't like it, we'll refund your purchase no questions asked.  Your purchases are safe!

The library and the source code are provided as-is.  The source can be modified, but not resold.  The license is a corporate license and is valid for any number of web servers, any number of software programs, and any number of developers inside a single company. 

Seen enough?  Buy it already, and save your company money over other bloated EDI libraries and the time spent developing your own library!

Questions?  Email us at ryanwhitaker@gmail.com

Frustrated because you can't find any simple EDI libraries to use with .NET?

We hear you. We couldn't find any either. So, we ended up creating our own after doing a lot of research. We've come up with a simple EDI library that makes it easy to create almost any kind of EDI document you'd ever need.

Big on simple features

Here is what DotNetEDI includes:

  • Build any kind of EDI document.
  • Includes a handful of implemented document types, such as 850 Purchase Orders, 855 Acknowledgements, and 810 Invoices. Includes base classes that you can override to your heart's content.
  • Written in nice, shiny .NET 2.0/3.0 for inclusion in any of your projects.
  • The source code. All of it.

Here is what DotNetEDI doesn't include:

  • It doesn't provide the means to deliver your EDI documents. There are so many different ways to deliver EDI that it didn't make sense to include it. FTP, SFTP, VANs, AS2, oh my! If you're using FTP, use .NET's built-in FtpWebRequest class, if you're using SFTP use SharpSSH, and if you're using any other method, chances are the provider has their own communications library already written for you.
  • It doesn't convert EDI documents to XML. Most places don't use XML, so the lack of this feature doesn't hurt. It wouldn't be difficult, however, to tack it on.

You get the source code, too.

You heard us. Stop poking around Reflector to see what's going on under the covers and just take a look at our source code. We don't have anything to hide!

An example of DotNetEDI's usage

Check out how easy it is to use! Let's create a purchase order:

// create the doc
PurchaseOrder doc = new PurchaseOrder();
doc.Interchange.Sender = customerID;
doc.Interchange.Date = DateTime.Now;

// create the functional group
FunctionalGroup group = doc.Interchange.NewFunctionalGroup();
group.FunctionalIdentifierCode = "PO";
group.Receiver = "AD2153819";
group.Date = date;
group.Control = orderID;
group.IndustryCode = "X";
group.IndustryID = "003030";
group.Sender = sender;
doc.Interchange.Add(group);

// create the transaction set
TransactionSet set = group.NewTransactionSet();
set.ID = "850";
set.Control = orderID;
group.Add(set);

// add beginning segment to transaction set
BeginningSegment beg = new BeginningSegment(doc);
beg.Purpose = "00";
beg.Type = "NE";
beg.Number = orderID;
beg.Date = date;
set.Add(beg);

// add line items to transaction set
foreach (OrderItem item in this.Order.Items)
{
LineItem lineItem = doc.NewLineItem();
lineItem.ID = string.Empty;
lineItem.Quantity = item.Quantity;
lineItem.Unit = "UN";
lineItem.UnitPrice = item.Price;
lineItem.ServiceID1Qualifier = "VN";
lineItem.ServiceID1 = item.ItemID;
set.Add(lineItem);
}

// add the count to the end of the transaction set
set.Add(doc.NewRecord("CTT", this.Order.Items.Count.ToString()));

// convert the order to a string
this.orderDocument = doc.ToString();

Only $499