What is Framework EDI .NET Hybrid?

The FREDI .NET hybrid allows application development in a .NET environment using features in Framework EDI.  Although it is still possible to use all the features of the ActiveX/COM, this is not desired because this requires interfacing between the .NET managed code and the ActiveX/COM using interop.  Using the interop dramatically degrades performance because data is marshaled between managed data to native data frequently.  The .NET hybrid in contrast marshals data less.

For the developer the FREDI hybrid functions in all respect like a true .NET assembly during development.  However, it still lacks attributes that make it a true .NET assembly (hence the term hybrid).  The FREDI hybrid is not an isolated application.  It is currently part of the entire FREDI SDK and is dependent on the DLLs and COM components that install with the SDK.  That means it is not an assembly that can be executed side-by-side with a previous version already existing in the system.  When a new FREDI SDK is installed, an older version of a component is replaced by a later version of the component.   That is, there can only be one version of the component in the system.  This is true also for the FREDI .NET hybrid.

See Also

• Programming with FREDI .NET Hybrid
• What is Framework EDI?
• Standard Exchange Format (SEF) File
• Framework EDI Object Hierarchy