NOTE: The components installed by the FREDI installers may change from one version
to the next. The components listed in this documentation apply to this version
only.
When installing, a path has to be specified as the target folder where all
the files are to be copied to. The target folder is further subdivided
into the following:
BIN. This folder contains the core library, program
executables and documentation that make up the product.
SAMPLE. This folder contains the sample programs if any are
provided. Otherwise this folder is not created.
TEMP. This folder may or may not be created. The programs initially determines the user's temporary folder first and
uses that folder for temporary files, otherwise the TEMP folder is created
under the target path.
WARNING: If the TEMP folder is created, DO
NOT save important files in the TEMP folder. Files will be erased under this
folder. Also, the TEMP folder could be
completely deleted when the FREDI product is uninstalled, erasing all files and folders
created in it.
The following components are installed to the target path.
Edidev_SEC.dll. This file is the Standard Error Code library
that provides description of errors generated during the operation of the
product. If this DLL is missing, the error generated will not have an
error description, and in some cases, the program may abnormally
terminate. This DLL must be located in the same path as the component
or executable file that is using it, and it should always be
located in the installed folder. This file is installed by all product
installer, and must be deployed with the application.
EDIdEvHelp6Alpha.chm. This file is the on-line documentation.
The following DLLs are self-registering, and by default, are located in the
installed folder. However, these DLLs can be moved anywhere as long as
they are self-registered in the location where they reside. By
self-registering, the location path of the DLL is recorded in the registry where
client applications can get the information to load the DLL.. Some DLLs do require that the Standard
Error Code file (Edidev_SEC.dll) must be in the same path otherwise an error
will be generated.
Fredi.dll. This file is the ActiveX/COM component of FREDI. This is the DLL that the client interfaces to use EDI, SEF, and
other general functions to create a full blown e-business application.
This component is installed in most installer editions, except for those
that require the desktop utilities only.
Fredi.x64.dll. This is the same as fredi.dll but for
64-bit installations only.
Fredi.tlb. Used in conjunction with fredi.dll, this file is the type library for the
FREDI (fredi.dll). Mostly required for development to enumerate objects,
methods and properties of EDI objects in a development environment. No
error is generated if this file is missing, but, if present, it must be in
the same folder as fredi.dll to be registered properly.
Fredi.x64.tlb. Same as fredi.tlb but for 64-bit installations
only.
To manually register, or unregister these DLLs, use the REGSVR32.EXE utility that comes with the Windows
operating system.
EDIdEv.FrameworkEDI.NET.dll is the .NET assembly for .NET programs.
This file is the core component for .NET applications that use EDI, SEF, and
general functions required to build full blown e-business applications. At
installation it is
automatically installed into the Global Assembly Cache (GAC). This component is installed in most installer editions, except for those
that require the desktop utilities only. To manually install the file to the GAC, use the GACUTIL.EXE utility. Example,
gacutil /i EDIdEv.FrameworkEDI.NET.dll
EDIdEv.FrameworkEDI.NET.x64.dll is for 64-bit installations only.
The program executable responsible for uninstalling FREDI is Edidev_SDK_Uninstall.exe.
This is the executable invoked when selecting to uninstall "Edidev
Framework EDI" in the "Add or Remove Programs" of the Control
Panel. Currently it uninstalls any existing copies of FREDI components that
have been installed in the target folder specified under the following registry entry
If any Program Menu has been specified in the same key, it is removed as
well.
There are 4 possible ways a product can be uninstalled.
When a runtime installer is executed from the command line, any previous
installation of FREDI is uninstalled.
When running an installer using the GUI interface, if a previous
installation is detected, a wizard dialog box will show an option to "Remove"
the previous installation. Selecting the "Remove" option will completely
uninstall the previous operation.
Invoking the "Add or Remove Programs" from the control panel, and then
selecting "EDIdEv Framework EDI" will uninstall the previous
installation.
Manually running the Edidev_SDK_Uninstall.exe
file directly on the target folder. No command line parameter is
required. Information on what gets uninstalled is read
from the Software\Edidev key of the registry.
When the product is uninstalled, the components are deleted from the
folder where they were originally installed. All components self-registered are
first unregistered before getting deleted. The .NET component is removed
from the GAC. All registry entries created by the product are also removed.
NOTE: Any system or shared file replaced, or added, are not deleted or reverted
to the older version. Please see System and Shared Files.
For applications and components to function properly, certain setup and
state information are stored in the registry. For 32-bit
installers installing on 32-bit Windows, registry
keys are created directly under the HKEY_LOCAL_MACHINE (HKLM) and/or
HKEY_CURRENT_USER (HKCU) registry hives. However, the same
registry keys are redirected into a separate logical registry view by
64-bit Windows. This separate logical registry view is mapped to a
subnode called Wow6432Node, which is created
automatically by the WOW64 component of the operating system, so that a
registry key in 32-bit created in "HKLM\Software\Edidev" would
be redirected to"HKLM\Sotware\Wow6432Node\Edidev".
The following registry keys are created by FREDI Installers:
Software\Edidev. This registry key is created to contain
general setup and state information for all Edidev
applications. In 32-bit Windows, the key is created in:
HKLM\Software\Edidev
HKCU\Software\Edidev
In 64-bit Windows, the same registry key is redirected to:
HKLM\Software\Wow6432Node\Edidev
Software\Edidev\Setup.x86\UninstallInfo. This registry key is
created to contain information for all files that have been
installed. If the files are to be later uninstalled, the
uninstaller utility Edidev_SDK_Uninstall.exe will read
the list of files in this registry hive to remove them from the
system. In 32-bit Windows, the key is created in:
In 64-bit Windows, the same registry key is redirected to:
HKLM\Software\Wow6432Node\Edidev\Setup.x86
Software\Microsoft\Windows\CurrentVersion\RunOnce. If an existing file denies access to an update then the new file is
recorded to be updated later after the computer restarts. In this case,
the installation is not completed until after the computer has rebooted, the
user has logged on, and the small utility program Edidev_SDK_RunOnce.exe
is executed. The program executable is entered in this registry
key. After the user has logged on, the system takes note of the
executable to run, deletes the registry entry, and then runs the
executable. This guarantees that the program is ran only once, after
which the installation is complete. The Edidev_SDK_RunOnce.exe utility
program registers FREDI components installed after restart.
Software\Microsoft\Windows\CurrentVersion\Uninstall\Edidev
(32-bit). To uninstall FREDI from the "Add or Remove Programs" in the control
panel, the installer records an uninstaller utility
program in this registry key. The name of the program is Edidev_SDK_Uninstall.exe
and is labeled as "EDIdEv Framework EDI".
