Runtime Redistributable & Utilities Installer (32-Bit)

The Runtime Redistributable & Utilities installs components required to run an application using Framework EDI interfaces and .NET classes, and also installs the Edidev eFileManager and eAnalyzer utilities.

• Executable Name
• Components Installed
• Utilities Installed
• Executing Installer in a Program
• Sample

NOTE: The components installed by the runtime setup may change from one version to the next. The components listed in this documentation apply to this version of Framework EDI only.
NOTE: This installer updates existing System and Shared Files, and modifies the Registry.

Executable Name:

• Edidev_FREDI_Runtime_Utility.exe
  

Components Installed

The following Framework EDI files are installed in the BIN subdirectory of the target path that the user had specified. When upgrading, these files will overwrite older versions of the existing files. Some components are dependent on one another and therefore they must be installed and registered in the order shown below. The installer takes care of the order in which these file are installed.

• Edidev_SEC.dll – Standard Error Code reference component.
• Edidev_UN1AD02B.dll – UN/EDIFACT codes description (Self-Register).
• Edidev_UNDED.dll – UN/EDIFACT reference library (Self-Register).
• Edidev_X121A4012.dll – ASC/X12 codes description (Self-Register).
• Edidev_X12DED.dll – ASC/X12 reference library (Self-Register).
• Edidev_Dictionary.dll – Standard Reference Library component (Self-Register).
• Edidev_SEF.dll – Standard Exchange Format component (Self-Register).
• Fredi.dll – Framework EDI core component (Self-Register).
• EDIdEv.FrameworkEDI.NET.dll - Framework EDI .NET hybrid (GAC).
• Edidev_SDK_RunOnce.exe – Installer Run-Once utility.
• Edidev_SDK_Uninstall.exe - Framework EDI uninstaller program.

The .NET Hybrid is installed to the global assembly cache (GAC).  The installer will replace an existing Framework EDI .NET hybrid with a later version.

• EDIdEv.FrameworkEDI.NET.dll

For more information on how these components are installed see Configuring Components

Utilities Installed

The following Framework EDI utilities are installed on the server on the target path specified.

• eFileManager.exe - EDI file manager utility.
• eAnalyzer.exe - EDI file analyzer utility.

Executing Installer in a Program

The Framework EDI  Runtime Setup can be executed in a program that can run an external program. Any previous installation of the product is always uninstalled before the any components are installed.  The syntax of the call is as follows:

• Edidev_FREDI_Runtime.exe –s<Serial Number> -p<Target Path> -m<Program Group> [-w]

Where:

• -s specifies the serial number of the product, 
• –p specifies the target path to install the files,
• -m specifies the program menu group name, and
• -w (optional) specifies that no shared system files are installed or updated.

Example:

    Edidev_FREDI_Runtime_Server.exe –s123456ABCDEFGH –pC:\Program Files\Edidev -mEdidev SDK

Where "123456ABCDEFGH" is the serial number, "C:\Program Files\Edidev" is the target path, and "Edidev SDK" is the menu group under which the utilities will be displayed in the menu.  Please note that the serial number MUST NOT contain any dashes or hyphens.  That is, a serial number like "1234-56AB-CDEF-GHIJ" is not allowed.

If there are no parameters following the executable in the command line, the program will launch a GUI interface to allow interactive installation.



Sample Visual Basic program

The following is a sample Visual Basic program to execute the setup.

Option Explicit

Private Type PROCESS_INFORMATION
   hProcess As Long
   hThread As Long
   dwProcessId As Long
   dwThreadId As Long
End Type

Private Type STARTUPINFO
   cb As Long
   lpReserved As String
   lpDesktop As String
   lpTitle As String
   dwX As Long
   dwY As Long
   dwXSize As Long
   dwYSize As Long
   dwXCountChars As Long
   dwYCountChars As Long
   dwFillAttribute As Long
   dwFlags As Long
   wShowWindow As Integer
   cbReserved2 As Integer
   lpReserved2 As Long
   hStdInput As Long
   hStdOutput As Long
   hStdError As Long
End Type

Private Declare Function CreateProcess Lib "kernel32" Alias "CreateProcessA" _
   (ByVal lpApplicationName As String, _
   ByVal lpCommandLine As String, _
   lpProcessAttributes As Any, _
   lpThreadAttributes As Any, _
   ByVal bInheritHandles As Long, _
   ByVal dwCreationFlags As Long, _
   lpEnvironment As Any, _
   ByVal lpCurrentDriectory As String, _
   lpStartupInfo As STARTUPINFO, _
   lpProcessInformation As PROCESS_INFORMATION) As Long

Private Declare Function OpenProcess Lib "kernel32.dll" _
   (ByVal dwAccess As Long, _
   ByVal fInherit As Integer, _
   ByVal hObject As Long) As Long

Private Declare Function TerminateProcess Lib "kernel32" _
   (ByVal hProcess As Long, _
   ByVal uExitCode As Long) As Long

Private Declare Function CloseHandle Lib "kernel32" _
   (ByVal hObject As Long) As Long

Private Declare Function WaitForSingleObject Lib "kernel32" (ByVal _
      hHandle As Long, ByVal dwMilliseconds As Long) As Long

Private Const SYNCHRONIZE = 1048576
Private Const NORMAL_PRIORITY_CLASS = &H20&
Private Const INFINITE = -1&


Private Sub Command1_Click()
    Dim pInfo As PROCESS_INFORMATION
    Dim sInfo As STARTUPINFO
    Dim lSuccess As Long
    Dim lRetValue As Long

    sInfo.cb = Len(sInfo)
    lSuccess = CreateProcess(vbNullString, _
                " Edidev_FREDI_Runtime_Utility –s123456ABCDEF -pC:\Program Files\Edidev", _
                ByVal 0&, _
                ByVal 0&, _
                1&, _
                NORMAL_PRIORITY_CLASS, _
                ByVal 0&, _
                vbNullString, _
                sInfo, _
                pInfo)

    ' Wait for the shelled application to finish
    lRetValue = WaitForSingleObject(pInfo.hProcess, INFINITE)

    lRetValue = CloseHandle(pInfo.hThread)
    lRetValue = CloseHandle(pInfo.hProcess)

    MsgBox "Setup Completed"
End Sub