Creating a Visual Studio Runtime Library Package Feature

The JD Edwards EnterpriseOne package build feature makes it possible to distribute third party applications with the deployment of a client package. Create a package feature for the Microsoft Visual C++ compiler runtime libraries to leverage this facility.

The Deployment Server should have a copy of the compatible vc_redist.x64.exe, vc_redist.x86.exe,vcredist_x64.exe, or vcredist_x86.exe . The actual names depend on the version of Microsoft Visual Studio that is installed. The x64 indicates that this installs 64-bit runtime libraries. The x86 indicates that this installs 32-bit runtime libraries-which is exactly what JD Edwards EnterpriseOne needs because the JD Edwards EnterpriseOne programs on the Development Client are 32-bit programs. For example, the Runtime Libraries installer for the 2013 compiler release is:

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Redist\MSVC\14.36.32532\vc_redist.x64.exe

Whereas, the installer for 32-bit libraries is:

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Redist\MSVC\14.36.32532\vc_redist.x86.exe

Note the string 12.0 in the path even though it is for Visual Studio 2013.

To create a Visual Studio runtime library package feature:

  1. On the deployment server, open Windows Explorer and navigate to your JD Edwards EnterpriseOne solution's shared folder. For example, E920.

  2. Expand the shared node and open OneWorld Client Installs\ThirdParty.

  3. Under the folder ThirdParty, create a new folder with the name VS20xxRTL (xx is equal to the current version).

  4. Locate and copy the appropriate vc_redist.x64.exe, vc_redist.x86.exe, vcredist_x64.exe, or vcredist_x86.exe file from your installed compiler path.

  5. Paste the executable file into the VS20xxRTL folder.

  6. Log into the deployment server's DEP900 environment.

  7. Fast path to menu GH9083, Package and Deployment Tools, and select the Package Assembly application.

  8. On the Work with Packages form, select Form and then Features.

  9. On the Work with Features form, click Add.

  10. Click Next to begin the Feature Based Deployment Director.

  11. On the Feature Information form, complete these fields and click Next:

    Field

    Value

    Feature

    VS20xx_RTL

    where you will replace xx with the version number.

    Feature Type

    1

    Description

    Visual C++ 20xx Runtime Libraries

    where you will replace xx with the version number.

    Feature Installation Options

    Required

    Components

    Additional Install Processes

  12. On the Additional Install Processes form, select the Execute After Install option.

  13. Complete these fields and click Next:

    Field

    Value

    Third Party

    VS20xxRTL

    Description

    Visual C++ 20xx Runtime Libraries

    where you will replace xx with the version number.

    Sequence

    1

    Executable Name

    vcredist_x64.exe (for 64-bit Development Clients)

    vcredist_x86.exe (for 64-bit Development Clients)

    This is the name of the executable file found in this directory:

    ...\ThirdParty\VS20xxRTL

    Source Path

    \\<deploymentservername>\E900\OneWorld Client Install\ThirdParty\VS20xxRTL

    Note: Do not use the Select Directory browse function to obtain the aforementioned path. Instead type the UNC path or cut and paste the Universal Naming Convention (UNC) path from Windows Explorer into the Source Path field.

    Parameters

    /Q

    /Q denotes Quiet Mode and does not require any user intervention.

  14. Click Save to preserve the feature settings and then click Next to continue.

  15. On the Feature Summary form, click End to complete the feature definition.

Note:

If you expand the nodes describing each package feature you may inspect the feature definition. You may notice that the UNC share path has been truncated for your newly created entry. This is NOT an issue as this line entry serves only as a description. The complete UNC share path has been properly preserved in System table F96604.