Files Required for Distribution

Files Required when Distributing Software with Codejock Components

When distributing software that includes components from Codejock Software, the following files should be installed on the client machine:

OCX files for each Codejock control used.
If installing on Windows 95 or Windows NT, then mfc42.dll must be installed.

Files to Distribute in Addition to the OCX Files

If you use the Chart Control, you will need to include GDIPlus.dll. This file is NOT included on Windows 2000 and earlier. By default, it is included on Windows XP and newer.
If you use Command Bars and created your CommandBar with the Command Bars Designer Studio, then you need to include the XCB or XML file that the Designer Studio created for you. The LoadDesignerBars method is used to load the XCB file. Both the LoadStateFromString and LoadStateFromXMLString methods will load a string that contains the state of the CommandBars. If you store the string in an external file, you will need to include this file.
If you use the LoadBitmap, LoadIcon, or AddIcon (if the icon is obtained externally) methods to load your image files, you will need to include the image files.
If you use the Resource property of the GlobalSettings class to provide language support for languages other than English, then you must include the language DLL for each language you support.
The XML features require Internet Explorer 5.0 or later to be installed on the client machine. Alternatively, you can include the msxml3.dll file with your installation.

Additional Notes

Each OCX file must be installed and registered for each Codejock control used on the client machine. The OCX files are the only files required to be installed on the client machine, with the exception of those noted in the "Files to Distribute in Addition to the OCX files" section above. If you plan to support UNICODE, then you must compile your project using the UNICODE version of the OCX and distribute the UNICODE OCX on the client machine.
You can install the OCX files in any location.
OCX registration is done with the regsvr32 tool. If your installer supports this, then you can have your installer register the OCX files for you.
There are some situations where you may need to include the content of the LIC file in your control using the License property. You DO NOT include the actual LIC file. For example, if you are developing an ActiveX control for Internet Explorer, you will need to include the license information using the License property.

The 2 Most Common Times This is Needed:

If you are using Visual Studio 2003 or above with C# or VB.NET, then you will need to embed the LIC information.
If you create the Codejock object in code (i.e., call CreateObject and did not place the control on a form), in this case, you must embed the LIC information within the scope of the object it is created.

The License property is located in the GlobalSettings class for each control. The code below illustrates how to use the License property for each control used:

IMPORTANT: Replace the XXX-XXX-XXX-XXX in the following code with the correct LIC code from your CURRENT version. This MUST be updated each time you upgrade your version of Codejock controls. The LIC string will ALWAYS CHANGE each time a new release is out.

VB6 Code

CommandBarsGlobalSettings.License = "CommandBars Control Copyright (c) 2003-2015 Codejock Software" & vbCrLf & _
                                    "PRODUCT-ID: Codejock.CommandBars.ActiveX.v24.0" & vbCrLf & "VALIDATE-CODE: XXX-XXX-XXX-XXX"
DockingPaneGlobalSettings.License = "DockingPane Control Copyright (c) 2003-2015 Codejock Software" & vbCrLf & _
                                    "PRODUCT-ID: Codejock.DockingPane.ActiveX.v24.0" & vbCrLf & "VALIDATE-CODE: XXX-XXX-XXX-XXX"
PropertyGridGlobalSettings.License = "PropertyGrid Control Copyright (c) 2003-2015 Codejock Software" & vbCrLf & _
                                     "PRODUCT-ID: Codejock.PropertyGrid.ActiveX.v24.0" & vbCrLf & "VALIDATE-CODE: XXX-XXX-XXX-XXX"
GridControlGlobalSettings.License = "Grid Control Copyright (c) 2003-2015 Codejock Software" & vbCrLf & _
                                      "PRODUCT-ID: Codejock.GridControl.ActiveX.v24.0" & vbCrLf & "VALIDATE-CODE: XXX-XXX-XXX-XXX"

C# Code

public frmMain()
{
    XtremeCommandBars.CommandBarsGlobalSettingsClass CommandBarsSettings = 
        new XtremeCommandBars.CommandBarsGlobalSettingsClass();

    CommandBarsSettings.License = 
        "CommandBars Control Copyright (c) 2003-2015 " +
        "Codejock Software\r\n" +
        "PRODUCT-ID: Codejock.CommandBars.ActiveX.v24.0\r\n" +
        "VALIDATE-CODE: XXX-XXX-XXX-XXX";  

    //
    // Required for Windows Form Designer support
    //
    InitializeComponent();
}

VB.NET Code

Public Sub New()
    MyBase.New()

    Dim CommandBarsSettings As _
        XtremeCommandBars.CommandBarsGlobalSettingsClass = _
        New XtremeCommandBars.CommandBarsGlobalSettingsClass

    CommandBarsSettings.License = "CommandBars Control Copyright (c) " + _
    "2003-2015 Codejock Software" + ControlChars.CrLf + "PRODUCT-ID: " + _
    "Codejock.CommandBars.ActiveX.v24.0" + ControlChars.CrLf + _
    "VALIDATE-CODE: XXX-XXX-XXX-XXX"

    'This call is required by the Windows Form Designer.
    InitializeComponent()

    'Add any initialization after the InitializeComponent() call
End Sub

You will need to provide the correct Product ID and Validate Code. This information can be found in the LIC file. The LIC file is located in the same location as the OCX file. By default, the location of the OCX and LIC file is ..\Codejock Software\ActiveX\Xtreme Suite\Bin for the Suite Pro installation. This code should be placed in the Form_Initialize event of the main form.

IMPORTANT: The LIC must match EXACTLY down to carriage returns, line feeds, and CASE; this is one of the most common mistakes made when embedding license information. The other common mistake is to not replace the "X"s in the sample code or not updating the license information when upgrading versions.

Supported Windows Versions

Windows 11
Windows 10
Windows 8.1
Windows 8
Windows 7
Windows Vista
Windows XP
Windows Me
Windows 2000
Windows 98 SE
Windows 98
Windows 95
Windows Server 2019
Windows Server 2016
Windows Server 2012 R2
Windows Server 2012
Windows Server 2008 R2
Windows Server 2008
Windows Server 2003 R2
Windows Server 2003
Windows Server 2000
Windows NT 4.0

Send feedback!