Copyright © 1998-2013 MultiMedia Soft

Files to be included with your application

Previous pageReturn to chapter overviewNext page

 

Important note about installed version

 

This section of the documentation applies to the full purchased version only: the trial version of the component comes with an internal protection schema against fraudulent uses which will reset properties of 3D buttons and will turn them into black or gray rectangles when the component is redistributed outside of the development machine where the trial version was originally installed through the provided setup program.

 

Files that your application needs to redistribute depends upon the platform target:

 

If compiling specifically for x86 (this is the unique option when compiling the container application through Visual Studio 4, 5, 6, 2002 or 2003)

  - the x86 version of the the control's binary 3DABM9U.OCX

 

If compiling for "Any CPU" (the container application needs to be compiled through Visual Studio 2005 or higher)

  - the x86 version of the the control's binary 3DABM9U.OCX

  - the x64 version of the the control's binary 3DABM9U64.OCX

 

If compiling specifically for x64 (the container application needs to be compiled through Visual Studio 2005 or higher)

  - the x64 version of the the control's binary 3DABM9U64.OCX

 

If you installed 3D Active Button Magic inside the default "C:\Program files\3D Active Button Magic" folder, you will find mentioned files inside the "C:\Program files\3D Active Button Magic\Redist" sub-folder.

IMPORTANT NOTE: Be careful not redistributing the 3DABM9U.OCX file available inside the "C:\Program files\3D Active Button Magic" main folder: this file is provided with the only purpose of avoiding a bug affecting Borland Delphi and Borland C++ Builder.

In order to improve performance, we have adopted Microsoft GDI+ technology. This means that if your target PC operating system is Windows XP or later version, you will not have to redistribute any other DLL because this technology is already included.

If you are targeting a previous operating system, such as Microsoft Windows NT® 4.0 SP6, Windows 2000, Windows 98 and Windows Millennium Edition, you will have to verify the presence of the GDIPLUS.DLL file or, alternatively, to redistribute it with your application. Microsoft strongly recommends against putting GDIPLUS.DLL in system folders to avoid "DLL hell" problems, so you should put GDIPLUS.DLL into your application folder or, alternatively, inside a non-system folder and add the path to this folder to the environment variable PATH.

Microsoft states that GDIPLUS.DLL is not compatible with Windows 95 and versions of Windows NT® 4.0 without SP6 installed.

SPECIAL NOTE A: Due to the fact that this control is fully UNICODE compliant, if you install the 3DABM9U.OCX file on Windows 98 or Windows ME you will need to redistribute also the UNICOWS.DLL file with your application; this file must be installed in the same directory of 3DABM9U.OCX (do not install it in the Windows\System32 folder or the control will not register correctly on the target system).

For your convenience, you will find the UNICOWS.DLL file inside the same folder in which you installed 3D Active Button Magic (default C:\Program files\3D Active Button Magic).

SPECIAL NOTE B: In order for the control to register and work correctly on the target system, the following is a summary of the Microsoft Windows libraries that must be available on the target system (usually you won't need to redistribute them):

WINMM.DLL

MSACM32.DLL

OLEAUT32.DLL

OLEPRO32.DLL

WININET.DLL

URLMON.DLL

GDIPLUS.DLL (only for operating systems older than Windows XP)

UNICOWS.DLL (only for Windows 98 and Windows ME operating systems)