Please read this entire file before deploying Borland Developer Studio 2006 applications, components, or libraries. This file is provided pursuant to the Borland License Terms and provides information on deploying Borland Developer Studio 2006 applications.
1. General Application Deployment
2. Components, Assemblies, and Packages
2.1 Distributing Custom Assemblies and Packages
2.2 Borland Runtime Assemblies and Packages
2.3 Runtime Assemblies and Packages
3. The Borland Database Engine (BDE)
5. ASP.NET Application Deployment
6. WebSnap Application Deployment
9. Data Compression Library (zlib)
11. Microsoft .NET SDK Runtime Assemblies
13. Removed or Modified Redistributable Files
Any .NET application that you build with Borland Developer Studio 2006 needs to run in an environment that has the Microsoft .NET Framework v1.1 redistributables installed. Please see the standard licensing information that ships with the Microsoft .NET Framework application to determine what assemblies are redistributable.
When building .NET applications using Borland Developer Studio 2006, provide your executable file and any assemblies not included in the .NET framework runtime that it calls. If you used runtime assemblies not included in the .NET Framework runtime with your application, be sure to include all required assemblies with your distribution.
C++ applications do not require a runtime interpreter DLL. All you have to provide is your .EXE file and any DLLs or BPLs that it calls. For simple applications you can distribute a standalone .EXE file. If you have used runtime packages with your application, be sure to include all required BPLs with the distribution. If you build using the dynamic Run-Time Library, you will also have to distribute one or more of the Run-Time Library DLLs CC3270.DLL or CC3270MT.DLL and the memory manager DLL.
For third party deployables, please see the third party documentation included with this product for other redistribution limitations.
If you distribute Borland Developer Studio 2006 assemblies or packages to other developers, be sure to supply the necessary files including .dll, .dcp, .dcpil, .dcu, .dcuil, .bpl, or executable files as required. Also, include any documentation you might have.
If you distribute C++Builder packages to other developers, be sure to supply both .BPI and any .LIB files to which your packages link. You will probably also want to include .OBJ and .DCU files as well as documentation. Package Collection (.DPC) files, created with the Package Collection Editor, offer a convenient way to distribute all the files associated with a package or group of packages.
In accordance with the "General Terms That Apply to Compiled Programs and Redistributables," you may redistribute Borland-supplied runtime assemblies and packages only for the purpose of executing Works created with Borland Developer Studio 2006. You may not modify these assemblies and packages in any way.
The redistributable runtime assemblies are installed in the GAC (Global Assembly Cache). These assemblies can be viewed in three ways:
· Navigate to either the [Common Files Directory]\Borland Shared\BDS\Shared Assemblies\4.0 directory or [Program Files Directory]\Borland\BDS\4.0\Bin directory. The assembly file location is dependent on whether the assembly is a shared assembly.
· Use the Microsoft .NET Framework 1.1 Configuration Wizard. You can access this wizard in Microsoft .NET Framework 1.1 by selecting Control Panel | Administrative Tools.
· Use the command-line tool, gacutil.exe, which ships with the Microsoft .NET Framework 1.1 SDK.
The redistributable runtime packages are installed in the system files directory of the computer, which is commonly WINDOWS\System32 on Windows 2000 and Windows XP computers.
Although this software may include assemblies and packages other than those listed below, only the assemblies and packages identified below as redistributable may be redistributed by you. For third party deployables, please see the third party documentation included with this product for other redistribution limitations.
You may NOT redeploy Borland-supplied design-time only assemblies and packages. If an assembly or package is not listed in this document then it is considered a design-time only assembly or package. You may not recompile or redistribute any Borland-supplied components or libraries for use by other developers.
Assemblies and packages that you develop may not have the same names as Borland-supplied assemblies or packages.
If you distribute component libraries or other packages, it is recommended that you avoid using the default DCLUSR package name, since this will cause naming conflicts with other developers.
The following table lists the redistributable runtime .NET assemblies for each edition of Borland Developer Studio 2006. The redistributable files are marked with an X.
|
File |
Architect |
|
Professional |
|
Borland.Data.Common.dll |
X |
X |
X |
|
Borland.Data.DataSync.dll |
X |
X |
|
|
Borland.Data.Db2.dll, bdpdb225.dll |
X |
X |
|
|
Borland.Data.Interbase.dll, bdpint25.dll |
X |
X |
X (local use only) |
|
Borland.Data.Msacc.dll, bdpmsa25.dll |
X |
X |
X |
|
Borland.Data.Mssql.dll, bdpmss25.dll |
X |
X |
X (local use only) |
|
Borland.Data.Mysql.dll, bdpmys25.dll |
X |
X |
X (local use only) |
|
Borland.Data.Oracle.dll, bdpora25.dll |
X |
X |
|
|
Borland.Data.Provider.dll |
X |
X |
X |
|
Borland.Data.Sybase.dll, bdpsyb25.dll |
X |
X |
|
|
Borland.Delphi.dll |
X |
X |
X |
|
Borland.Eco.Core.dll |
X |
X |
X |
|
Borland.Eco.Handles.dll |
X |
X |
X |
|
Borland.Eco.Interfaces.dll |
X |
X |
X |
|
Borland.Eco.Ocl.ParserCore.dll |
X |
X |
X |
|
Borland.Eco.Persistence.Bdp.dll |
X |
X |
|
|
Borland.Eco.Persistence.dll |
X |
X |
|
|
Borland.Eco.Persistence.Multi.dll |
X |
|
|
|
Borland.Eco.Persistence.SqlServer.dll |
X |
X |
|
|
Borland.Eco.Persistence.Xml.dll |
X |
X |
X |
|
Borland.Eco.Web.dll |
X |
|
|
|
Borland.Eco.Windows.Forms.dll |
X |
X |
X |
|
Borland.VclAdoDb.dll |
X |
X |
X |
|
Borland.Vcl.dll |
X |
X |
X |
|
Borland.Vcl.Samples.dll |
X |
X |
X |
|
Borland.VclActnBand.dll |
X |
X |
X |
|
Borland.VclAdoNet.dll |
X |
X |
X |
|
Borland.VclBdeRtl.dll |
X |
X |
X |
|
Borland.VclDbCtrls.dll |
X |
X |
X |
|
Borland.VclDbExpress.dll |
X |
X |
X |
|
Borland.VclDbRtl.dll |
X |
X |
X |
|
Borland.VclDbxCds.dll |
X |
X |
X |
|
Borland.VclDSnap.dll |
X |
X |
X |
|
Borland.VclDSnapCon.dll |
X |
X |
X |
|
Borland.VclIBXpress.dll |
X |
X |
X |
|
Borland.VclInterop.dll |
X |
X |
X |
|
Borland.VclRtl.dll |
X |
X |
X |
|
Borland.VclX.dll |
X |
X |
X |
|
Borland.VclXmlRtl.dll |
X |
X |
X |
|
IndyCore.dll |
X |
X |
X |
|
IndyProtocols.dll |
X |
X |
X |
|
IndySystem.dll |
X |
X |
X |
|
Intraweb_80_100net.dll |
X |
X |
X |
|
Intrawebdb_80_100net.dll |
X |
X |
X |
|
Nevrona.Rave.Vcl.dll |
X |
X |
X |
The following table lists the redistributable Win32 runtime packages and DLLs for each edition of Borland Developer Studio 2006. The redistributable files are marked with an X.
|
File |
Architect |
|
Professional |
|
adortl100.bpl |
X |
X |
X |
|
bcboffice2k100.bpl |
X |
X |
X |
|
bcbofficexp100.bpl |
X |
X |
X |
|
bcbie100.bpl |
X |
X |
X |
|
bdertl100.bpl |
X |
X |
X |
|
cc3270mt.dll |
X |
X |
X |
|
dbxasa30.dll |
X |
X |
|
|
dbxase30.dll |
X |
X |
|
|
dbxinf30.dll |
X |
X |
|
|
dbxint30.dll |
X |
X |
X |
|
dbxmys30.dll |
X |
X |
X |
|
dbxora30.dll |
X |
X |
|
|
dbxdb230.dll |
X |
X |
|
|
dbxmss30.d |
X |
X |
X |
|
dbexpress100.bpl |
X |
X |
X |
|
dbrtl100.bpl |
X |
X |
X |
|
dbxcds100.bpl |
X |
X |
X |
|
dcloffice2k100.bpl |
X |
X |
X |
|
dclofficexp100.bpl |
X |
X |
X |
|
dsnap100.bpl (ClientDataSet Redistributable) |
X |
X |
X |
|
dsnapcon100.bpl (ClientDataSet Redistributable) |
X |
X |
|
|
dsnapent100.bpl (ClientDataSet Redistributable) |
X |
X |
|
|
dss100.bpl |
X |
X |
|
|
ibevnt100.bpl |
X |
X |
X |
|
ibxpress100.bpl |
X |
X |
X |
|
inet100.bpl |
X |
X |
X |
|
inetdb100.bpl |
X |
X |
X |
|
inetdbbde100.bpl |
X |
X |
X |
|
inetdbxpress100.bpl |
X |
X |
X |
|
Intraweb_80_100.bpl |
X |
X |
X |
|
Intrawebdb_80_100.bpl |
X |
X |
X |
|
midas.dll (ClientDataSet Redistributable) |
X |
X |
X |
|
Rave65VCL100.bpl |
X |
X |
X |
|
rtl100.bpl |
X |
X |
X |
|
soaprtl100.bpl |
X |
X |
X |
|
tee100.bpl |
X |
X |
X |
|
teedb100.bpl |
X |
X |
X |
|
teeui100.bpl |
X |
X |
X |
|
vcl100.bpl |
X |
X |
X |
|
Vclactnband100.bpl |
X |
X |
X |
|
vcldb100.bpl |
X |
X |
X |
|
vcldbx100.bpl |
X |
X |
X |
|
vclib100.bpl |
X |
X |
X |
|
vclie100.bpl |
X |
X |
X |
|
vcljpg100.bpl |
X |
X |
X |
|
Vclshlctrls100.bpl |
X |
X |
X |
|
Vclsmp100.bpl |
X |
X |
X |
|
vclx100.bpl |
X |
X |
X |
|
webdsnap100.bpl |
X |
X |
|
|
websnap100.bpl |
X |
X |
|
|
xerceslib.dll |
X |
X |
X |
|
xercesxmldom.dll |
X |
X |
X |
|
xmlrtl100.bpl |
X |
X |
X |
Borland Developer Studio 2006 applications that use the Borland Database Engine (BDE) for database access require that you distribute the BDE with the application.
In accordance with the Additional License Terms for BDE, you may distribute the BDE files with your application using a Borland-certified Redistributable Install program such as InstallShield Express or another compliant install program. You may redistribute only those BDE files selected by the Borland-certified installation program.
Additionally, Borland supplies a BDE merge module that is an approved mechanism for deploying BDE. This module may be used with any Windows Installer (MSI) development tool (such as InstallShield for Windows Installer, Wise for Windows Installer and others). The merge module includes the base BDE appropriate to the version of Borland Developer Studio 2006 purchased.
See the BDE Links deployment notes in the file BDEDEPLOY.TXT (found in the BDE directory) for specific information regarding deploying the BDE with database applications created in Borland Developer Studio 2006.
Borland Developer Studio 2006 includes a library of redistributable bitmap images normally installed in the subdirectory:
\Program Files\Common Files\Borland Shared\Images
Borland Developer Studio 2006 also includes a database EVENTS.DB with licensed images from PhotoDiscPhotoDisc, Inc. 1995 and may not be redistributed.
Any non-FCL (Framework Class Library) assemblies, such as the Borland Data Provider assemblies, must be deployed with your ASP.NET applications. For additional information about deploying ASP.NET applications, refer to http://msdn.microsoft.com/asp.net/using/deploying/default.aspx.
If you created your application as a Web App Debugger executable, you will first have to convert it to an ISAPI DLL or CGI executable. To deploy your DLL or EXE to a web server, you will have to place your application in a directory that has executable rights. With Internet Information Services (IIS) this is typically C:\Inetpub\Scripts. For each WebModule in your application, you must copy the associated HTML file to the same directory as your EXE/DLL. By default, the associated HTML file is simply the WebModule unit's name with .html as the extension.
WebSnap applications require the Microsoft Active Scripting Engine in order to work. It is included with Internet Explorer 5, and is installed by default on Windows 2000 machines. To download the Scripting Engine, visit: http://msdn.microsoft.com/scripting/
Borland Developer Studio 2006 Architect and Borland Developer Studio 2006
The Borland Developer Studio 2006 CD includes software for JPEG image compression and decompression. This software and its source code are distributed by the Independent JPEG Group and copyrighted by
The Borland Developer Studio 2006 CD includes zlib data compression software. This software and its source code are copyrighted by Mark Adler and others and may be used and distributed subject to the conditions specified in the file zlib.h.
The Windows common controls are provided in a Microsoft-approved installation file, 50comupd.exe. This file contains the common controls library, comctl32.dll. The only approved method for updating end-user computers is by the use of 50comupd.exe. This file can be redistributed with applications built using Borland Developer Studio 2006. No other method is permitted.
Please refer to the Microsoft .NET SDK license agreement to determine what Microsoft .NET SDK runtime assemblies are redistributable.
Any file, module or component not designated as redistributable in this document may not be redistributed, and is limited to use by you under the terms of the end-user license agreement accompanying this product.
Borland RESERVES THE RIGHT TO REMOVE OR MODIFY INDIVIDUAL REDISTRIBUTABLE FILES FROM THIS BORLAND SOFTWARE PRODUCT, AT ANY TIME PRIOR TO RELEASE OF THE PRODUCT, REGARDLESS OF WHETHER SUCH FILES CONTINUE TO BE LISTED AS "REDISTRIBUTABLE" UPON RELEASE OF THE PRODUCT. BORLAND SHALL HAVE NO OBLIGATION WHATSOEVER IN CONNECTION WITH ANY FILE WHICH IS LISTED AS "REDISTRIBUTABLE" BUT HAS BEEN REMOVED FROM THE PRODUCT PRIOR TO THE PRODUCT'S RELEASE.
Unless otherwise noted, all materials provided in this release are Copyright 2005 by Borland Software Corporation.