EDI Tools for .NET is a software development kit for .NET 9, .NET 8, .NET 6, .NET Core, and .NET Framework, which makes it straightforward to parse, generate, validate, acknowledge, split, customize, or in other words, programmatically manipulate EDI files. It is written in C# and is distributed as a DLL file and a NuGet package.

Download EdiFabric EDI Tools (including local NuGet packages and DLLs)

Download EdiFabric EDI Tools from GitHub

EDI Tools for .NET does not provide any communication components (AS2 or SFTP, for example), has no dashboard or UI, and is not a full end-to-end EDI solution.

Compatibility with .NET

.NET 6 +

Supports: macOS, Linux, Windows. Includes support for cloud hosting, including AWS and Azure

.NET Framework 4.5 +

Supports: Windows, Azure

NuGet package targets

The NuGet package targets the following versions:

• .NET Framework 4.5
• .NET Framework 4.8
• .NET 6.0
• .NET 7.0
• .NET 8.0
• .NET 9.0

Get started

To get started with EDI Tools for .NET you can:

1. If you prefer to play around, download a collection of C# examples that cover the product's full functionality (requires Visual Studio). Includes a demo project to translate EDI or flat files straight away.

2. Create a new project from scratch.
3. Head on to the step-by-step tutorial., for a more learn-by-doing approach.

Serial Key

To use EDI Tools for .NET, you need a valid serial key, and if you want to learn how the serial key works, go to this article.

The serial key is applied programmatically using the following code:

EdiFabric.SerialKey.Set("Valid Serial Key");

If you can't find your serial key or don't know how to apply it, contact us for assistance.

The same key can be used across all products that come with every EdiFabric plan - as the API key when accessing EdiNation or EdiNation InHouse and as the serial key when using EdiFabric EDI Tools.

Data Security

All operations provided by EDI Tools for .NET (including the AckMan plugin) run in the process that started them, and no data is sent or received during the execution. Your sensitive EDI data never leave your network. Read our privacy policy for more details. 

The only method that makes an external call is EdiFabric.SerialKey.Set to acquire a token from the authentication API. To test this in debug mode, add a breakpoint just after EdiFabric.SerialKey.Set, then turn off the network and resume the execution. Your EDI files/data will be processed in the same way as if the network was on.

Supported EDI Standards

EDI Tools for .NET currently supports all message types for the X12, EDIFACT, HL7, and NCPDP (SCRIPT and Telecommunications) EDI standards, the German automotive standard VDA, as well as custom formatted flat files (delimited, positional, or a mixture of both).

Each message type/transaction set is represented by what we call an "EDI Template", and you can learn more about EDI templates here.

The following EDI templates are available out of the box; however, if you can't find a particular transaction, please let us know.:

For an interactive view of all templates, go to EdiNation (no registration is required).