Borland Developer Studio 2006 Update 2 is now available

By: John Kaster

Abstract: The Delphi 2006, C++Builder 2006 and C#Builder 2006 update is now available for download by registered users

Higher performance and better quality

Where to get BDS 2006 Update 2

QualityCentral reports addressed in Update 2

Borland Developer Studio 2006, Update 2 Release Notes

Update Installation Instructions

Resolved Defects

Known Issues

General

C++

Compiler

ECO

IDE

.NET/BDE

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)

4. Sample Images

5. ASP.NET Application Deployment

6. WebSnap Application Deployment

7. Borland VisiBroker

8. Borland InterBase

9. JPEG Compression Software

10. Data Compression Library (zlib)

11. Windows Common Controls

12. Microsoft .NET SDK Runtime Assemblies

13. Other Components

13. Removed or Modified Redistributable Files

Borland Developer Studio 2006 Installation Notes

Minimum System Requirements

Detecting Pre-Requisites With The Bootstrap Utility

General Installation Notes

Multiple users on one machine

Installer may require a reboot

Installer may require additional temporary space

Assemblies installed in the Global Assembly Cache

Installing another edition of BDS 2006

Note to BDP .NET users

C++ Demos

Running Setup in Silent Mode

Silent Installation

Troubleshooting

Destination locations

Third-party Add-ons

Indy and Office Win32 package registration

Personality Selection

File Type Associations

Example

Silent Uninstallation

Modifying the Installed Product Using Add/Remove Programs

Installing Optional, Add-on Products

Borland CaliberRM SDK

ComponentOne Studio Enterprise for Borland Developer Studio

Wise Owl Demeanor for .NET, Personal Edition

Rave Reports Borland Edition (BE)

NUnit Unit Testing Framework

MDAC 2.8 SP1

Known Installation Issues

Uninstalling This Product

        Higher performance and better quality

We are pleased to announce the availability of Update 2 for Borland Developer Studio (BDS) 2006, also known as Delphi 2006, C++Builder 2006, and C#Builder 2006. Over 500 bug reports tracked by our internal system have been fixed in this release. Of the reports submitted by the community into QualityCentral, over 150 have been addressed in this update.

        Where to get BDS 2006 Update 2

This is a free update available to all BDS 2006 registered users for the Professional, Enterprise, or Architect versions. It can be downloaded from the following locations:

Borland Developer Studio (all) users site

Delphi registered users site

C++Builder registered users site

        QualityCentral reports addressed in Update 2

The Update 2 build number is 10.0.2288.42451. Update 2 work began with build versions of 10.0.22*, so QualityCentral searches with a "Resolved in Build" value of "10.0.22" will return all reports resolved for the update 2 builds. You can retrieve the complete list of fixes with the URL http://qc.borland.com/qc/wc/qcmain.aspx?search=1&rib=10.0.22. This search is currently indicating 151 QC reports have been resolved in Update 2.

The Update 2 readme is included in its entirety below:

        Borland Developer Studio 2006, Update 2 Release Notes

This file contains important supplementary information about the features and fixes that are included in this updated release of Borland Developer Studio 2006. Update 2 is a cumulative release, and contains all of the code from Borland Developer Studio 2006, plus the enhancements and fixes that were added for Update 1 and Update 2.

This file includes installation instructions for this update, information about issues that were resolved for Update 1 and Update 2, and information about issues that we are currently working on (known problems). This information may not appear in the main product documentation. Borland recommends that you read this file in its entirety.

In addition to this update, there is now a new version of Intraweb available on the Intraweb website, and there is an InterBase 7.5.1 SP1 update available for Windows, at the following website: InterBase 7.5.1 SP1.

For information about installation, deployment, and licensing issues, see the Install, Deploy, and License files located, by default, at C:\Program Files\Borland\BDS\4.0.

        Update Installation Instructions

Note: This update can only be applied to the English version of Borland Developer Studio 2006.

This update can be applied to either the initial release of BDS 2006 or BDS 2006, Update 1. This update cannot be removed. To uninstall this update, you will have to remove the full product and re-install the product, including Update 1 if necessary.

Close Borland Developer Studio 2006 before installing this update.

If you have MSI 3.0 or above, double-click on the .msp file to begin installation. Otherwise, navigate to the System32 folder in a command window and type the following to start the installation.

Type in the command line syntax for your MSI version.

Command line syntax for MSI 2.0:

msiexec.exe /p <path to bds2006_arch_upd2.msp file> /L*v <path to log file> DEBUG_MODE=ON REINSTALL=ALL REINSTALLMODE=omus

where:

/L*v and DEBUG_MODE=ON are optional.

For example, if you have the .msp file in C:\temp directory, then msiexec.exe /p "C:\temp\bds2006_arch_upd2.msp" REINSTALL=ALL REINSTALLMODE=omus will install the update.

The following example will also generate a log file named bds2006upd2.log under C:\temp
msiexec.exe /p "C:\temp\bds2006_arch_upd2.msp" /L*v "C:\temp\bds2006upd2.log" REINSTALL=ALL REINSTALLMODE=omus DEBUG_MODE=ON

Command line syntax for MSI 3.0 or above:

msiexec.exe /update <path to .msp file> /L*v <path to log file> DEBUG_MODE=ON

where:

/L*v and DEBUG_MODE=ON are optional.

For example, if you have the .msp file in C:\temp directory, then msiexec.exe /update “C:\temp\bds2006_arch_upd2.msp” /L*v “C:\temp\bds2006_arch_upd2.log” DEBUG_MODE=ON will install the update.

For more information on MSI command-line options, please visit Microsoft MSI Command Line Options.

The final dialog of the update installer indicates whether the update was successful. You can also verify using one of the following methods:

Open the Windows Control Panel, click Add/Remove Programs, and then choose the Borland Developer Studio 2006 product. Use the Click here for support information link and verify that the version is 10.0.2.

Open the registry using regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\BORLAND\BDS\4.0 and verify that the ProductVersion and UpdatePackInstalled string values are 10.0.2 and 2, respectively.

With the IDE open, choose Help | About to display the About dialog box. Verify that Update 2 appears after the product version number.

        Resolved Defects

To view the list of resolved defects for Borland Developer Studio 2006, Update 2, go to the following website: http://bdn.borland.com/article/0,1410,33463,00.html. To look up the resolution for specific bugs you have reported, you can go to the following website: http://qc.borland.com/wc/qcmain.aspx and look up the resolutions for defects you reported by Quality Central bug number.

        Known Issues

The following are known issues in Borland Developer Studio 2006, Update 2.

        General

The behavior of WideChar/String compatibility has changed in Borland Developer Studio 2006. Specifically, in Borland Developer Studio 2005, and earlier, the following function would produce the result TRUE. Now it produces FALSE.

function DoIt: Boolean;
var
  C: WideChar;
begin
   C := #0;
   if C = '' then
      Result := TRUE
  else
     Result := FALSE;
end;

This behavior is consistent with the behavior of the .NET compiler, but could break your existing code.

Similar behavior exists with AnsiChar in Win32, but that function has not yet been modified to be consistent with the .NET compiler, so it still produces a TRUE result.

There is some confusion about how to compile a SOAP server application when you are using Borland Developer Studio 2006 with Indy10.

To compile a SOAP server application using Indy10: include the VCL source in your project; add C:\Program Files\Borland\BDS\4.0\source\Win32\Internet;C:\Program Files\Borland\BDS\4.0\source\Win32\Indy9;C:\Program Files\Borland\BDS\4.0\source\Win32\soap to your search path; and recompile.

        C++

To resolve issues with C++ name-mangling when using C++ and Delphi together, a change has been made in the Delphi to C++ header file generation. This change may cause some of your existing code to not compile due to cast errors during the processing of the .HPP files, such as "Cannot convert..." or "Type mismatch in parameter...".

Three of the errors that commonly occur with this issue (or while trying to fix this issue) are:

Cannot convert 'TPropInfo * *' to 'TPropInfo * ( *)[16380]'

Type mismatch in parameter 'PropList' (wanted 'TPropInfo * ( *)[16380]', got 'TPropInfo * *')

and

Pointer to structure required on left side of -> or ->*



To correct these errors, it may be necessary to change the declaration type and/or add casts. For example, the following snippets of code show some typical changes that may be necessary to avoid errors.

Code created before Update 2:

TButton* btn = new TButton((void*)0);
  PTypeInfo TypeInfo = reinterpret_cast(btn->ClassInfo());
  PTypeData TypeData = GetTypeData(TypeInfo);
  PPropList PropList = new PPropInfo[TypeData->PropCount];
  GetPropInfos(TypeInfo, PropList);
  for( int i =0; iName));


needs to be changed to the following (so that it will work with and after Update 2):

TButton* btn = new TButton((void*)0);
  PTypeInfo TypeInfo = reinterpret_cast(btn->ClassInfo());

  PTypeData TypeData = GetTypeData(TypeInfo);
  PPropInfo* PropList = new PPropInfo[TypeData->PropCount];
  GetPropInfos(TypeInfo, (PPropList)PropList);
  for( int i =0; iName));



Compiling C++ Win32 source code that was previously generated via importing a Type Library, may result in these types of errors. Similarly, these errors can be resolved via casts or changes in type declaration. Alternatively, a new import using post-patch import tools will result in the necessary casts in the resultant generated source code.

For example, the following previously imported generated code results in an error:

TControlData TSomeControl::CControlData =
{
  TFontIDs, //Error E2034 Cannot convert 'int *' to 'int ( *)[65536]'


A re-import will result in casts in the generated code:

TControlData TSomeControl::CControlData =
{
  Activex::PDispIDList(TFontIDs), //No Error

        Compiler

Certain ActiveX projects may encounter an Internal Compiler Error (ICE) when compiling the project source of the project. (The project source of a project is the .cpp file that contains either the DllEntryPoint or WinMain routine). The error will typically be encountered on the line that creates an instance of a TComModule. The following snippet illustrates an example of such code:

#include <vcl.h>

#pragma hdrstop

TComModule _ProjectModule(0 /*InitATLServer*/);  << Compiler Error Here
TComModule &_Module = _ProjectModule;


This error is related to the compiler using precompiled header to instantiate the TComModule instance. To workaround this problem, move the ‘#pragma hdrstop’ directive to the very top of the .cpp file as shown below:

#pragma hdrstop   << First line of project source
#include <vcl.h>

TComModule _ProjectModule(0 /*InitATLServer*/);  << Compiler Error Here
TComModule &_Module = _ProjectModule;


NOTE: The line above with the compiler error is slightly different for In-Proc servers: the object is constructed without the '0' parameter. However, the behavior is still the same.

If the solution above doesn't work then the most effective work around is to turn off the precompiled headers. Do this by going to Project, Options, C++ Compiler, Pre-compiled headers and uncheck -He, -H=, -Hc and -Hs. The next time you build you won't get an internal compiler error.

Also delete the external types files in the same directory. These files will have the extension #nn where n is a number. For example, if vcl100.csm is the name of the precompiled header, delete vcl100.#*.

        ECO

When upgrading an ECO II model to an ECO III model, the method AsIObject sometimes converts with the wrong visibility, strict private instead of public, possibly causing a compilation error. Should this happen, the visibility can be adjusted manually in the generated source; insert a line with the “public” access modifier directly before the AsIObject function, like:

public
    function AsIObject: IObjectInstance;

There is a known issue in the translation of Ocl expressions to SQL queries that occurs under some circumstances when navigating a relation from a loop-variable, such as:

Person.allInstances->select(home.address = 'myAddress')

This results in a stack overflow exception. This issue affects both OclPsHandle and IOclPsService.

        IDE

Some users are not able to drag and drop items successfully from the Tool Palette. If you are experiencing this issue, you may have to change the 'Show Windows contents while dragging' option on your computer. If you are using Windows 2000, open the Control Panel and choose Display | Effects. Make sure the 'Show Windows contents while dragging' option is enabled, and Apply your changes. If you are using WindowsXP, open the Control Panel and choose System. Click the Performance button. Select Settings. Make sure the 'Show Windows contents while dragging' option is enabled, and Apply your changes.

        .NET/BDE

If you're using the Borland Database Engine (BDE) within the Delphi.NET personality, meta data such as table names, field names, and stored procedure names are truncated if the name string uses international characters.

The deployment documentation is also included:

        Deploying Borland Developer Studio 2006 Applications

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

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.

        2. Components, Assemblies, and Packages

        2.1 Distributing Custom Assemblies and Packages

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.

        2.2 Borland Runtime Assemblies and 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.

        2.3 Runtime Assemblies and Packages

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

Enterprise

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

Enterprise

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

       

        3. The Borland Database Engine (BDE)

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.

        4. Sample Images

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.

        5. ASP.NET Application Deployment

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.

        6. WebSnap Application Deployment

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/

        7. Borland VisiBroker

Borland Developer Studio 2006 Architect and Borland Developer Studio 2006 Enterprise include a development license for VisiBroker (Borland Enterprise Server, VisiBroker Edition). This product does not include deployment rights for the VisiBroker CORBA ORB. When deploying an application requiring CORBA services, you must first obtain VisiBroker Deployment licenses, available separately from Borland. For more information on VisiBroker, see Borland's World Wide Web site at http://www.borland.com/besvisibroker/, or contact your local Borland sales office.

        8. Borland InterBase

Borland Developer Studio 2006 Architect, Borland Developer Studio 2006 Enterprise, and Borland Developer Studio 2006 Pro include a development license for InterBase (Borland InterBase 7.5.1, Developer Edition). This product does not include deployment rights for Borland InterBase server. When deploying an application requiring Borland InterBase server, you must first obtain InterBase Deployment licenses, available separately from Borland. For more information on InterBase, see Borland's World Wide Web site at http://www.borland.com/interbase/, or contact your local Borland sales office.

        9. JPEG Compression Software

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 Thomas G. Lane . For conditions of distribution and use, see the README file that accompanies the software.

        10. Data Compression Library (zlib)

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.

        11. Windows Common Controls

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.

        12. Microsoft .NET SDK Runtime Assemblies

Please refer to the Microsoft .NET SDK license agreement to determine what Microsoft .NET SDK runtime assemblies are redistributable.

        13. Other Components

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.

        13. Removed or Modified Redistributable Files

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.

And finally, the installation guide is included in this article as well:

        Borland Developer Studio 2006 Installation Notes

        Minimum System Requirements

The following Windows platforms are supported:

Microsoft Windows 2000 (SP2 or higher and security updates are recommended)

Microsoft Windows XP Professional

Microsoft Windows Server 2003

The latest SP and security updates are recommended for all platforms, including both XP and Server 2003.

Microsoft Internet Explorer 6.0 SP1 or later

NOTE: The English version of BDS 2006 updates Internet Explorer with the English version of Internet Explorer 6.0 SP1. If you are running a localized operating system, run Windows Update to ensure that you get the proper localized version of Internet Explore

BDS 2006 requires approximately 1.2 GB of disk space for full installation.

The .NET Framework version 1.1 requires approximately 150 MB of disk space.

The .NET Framework SDK version 1.1 requires approximately 850 MB of disk space.

Pentium II 450MHz or higher (Pentium III 850+ MHz recommended).

256 MB RAM (512 MB recommended)

CD-ROM drive

VGA or higher resolution monitor

Mouse or other pointing device

If you are using the Together product, you will need to install the JRE that is located on Disk 1 before installing. (The bootstrap utility described in the next section will not look for this software.) 

        Detecting Pre-Requisites With The Bootstrap Utility

The bootstrap utility detects whether the following BDS 2006 pre-requisites are installed on your system:

Microsoft Internet Explorer v6.0 SP1

Microsoft .NET Framework v1.1

Microsoft .NET Framework v1.1 SP1

Microsoft .NET Framework SDK v1.1

Microsoft XML Core Services (MSXML) v4.0 SP2

Microsoft Visual J# .NET v1.1 Redistributable

If you install BDS 2006 using the installation launcher (install.exe in the root directory on Disk 1), the bootstrap utility runs automatically.

However, if you install BDS 2006 using setup.exe in the "Install" directory on Disk 1, the bootstrap utility is bypassed. Borland recommends that you run the bootstrap utility before running setup.exe. Run prereqs.exe in the "Install" directory on Disk 1.

If the utility does not find the pre-requisite software on your system, it prompts you to install the software. Reply yes to the prompts to install the software required for BDS 2006 to function properly. If you reply no, the BDS 2006 installation will not continue if any of the pre- requisites are not found.

For StarTeam to function property, you will need to install VJ# hotfix. This is not installed as part of the prereqs.exe boostrap. It is available in the Info\StarTeam Hotfix folder in Disk 1 of the product.

If you install Microsoft .NET Framework v1.1 SP1 using the bootstrap utility, you will be prompted to reboot the machine after Microsoft .NET Framework v1.1 SP1 installation is complete. You can click No to the prompt and reboot after all installations are complete.

        General Installation Notes

        Multiple users on one machine

The product can be installed by any licensed user with Administrator privileges, and is immediately available to all licensed users of the same machine. It is also available to any licensed users you may add later.

        Installer may require a reboot

You will be prompted to reboot your system at the end of the BDS 2006 installation if you have chosen to install Internet Explorer 6.0 SP1 from the bootstrap utility (prereqs.exe) or Microsoft .NET Framework v1.1 SP1 or MDAC 2.8 from the BDS 2006 setup.

        Installer may require additional temporary space

If the drive containing the folder specified in your TEMP environment variable is low on space, the Installer may halt with an error message noting the shortage. If this occurs, you'll need to assign your TEMP variable to a folder on a drive with more disk space, then rerun the installation.

        Assemblies installed in the Global Assembly Cache

Duplicate copies of assemblies installed in the GAC are provided in the <CommonFilesFolder>\Borland Shared\BDS\Shared Assemblies\4.0 directory. If C:\ is your Windows drive, the default <CommonFilesFolder> is C:\Program Files\Common Files\.

The assemblies in the GAC can be used to test deployment. The duplicate copy of the assemblies in the above mentioned directory can be used for development purposes. You can also use the redistributable installer for deployment purposes. It is located on Disk 4.

        Installing another edition of BDS 2006

BDS 2006 stores assembly and Tool Palette configuration information in the file ApplicationSettings.xml, located in the user's home directory at "Documents and Settings\<username>\Local Settings\Application Data\Borland\BDS\4.0."

This file is not deleted during an uninstall and might cause assembly version errors in the IDE if you install another edition of BDS 2006 (for example, Enterprise or Architect) on the same machine. To avoid this problem, delete ApplicationSettings.xml BEFORE installing another product edition.

        Note to BDP .NET users

Setup will generate BdpDataSources.xml and bdpConnections.xml depending on the providers you choose during installation. At the end of the installation, setup will prompt you to overwrite or merge the bdpConnections.xml file if it exists in the destination directory. If you choose No at this prompt, the existing bdpConnections.xml file will be merged with the file being installed. If you choose Yes at the prompt, setup will replace the existing bdpConnections.xml file with the new file. By default, the bdpConnections.xml file is located at C:\Program Files\Borland\BDS\4.0\Bin.

        C++ Demos

Additional C++ demos are available in the Demos folder in Disk 4 of the product.

        Running Setup in Silent Mode

        Silent Installation

Note: Silent installation is not supported for maintenance installations (if you are using the Modify option in Control Panel -> Add/Remove Programs).

To run a silent installation (install from a command line without the use of a GUI wizard), change to the System32 directory, and type the following in a command window:

<System32Folder>\msiexec.exe /I <.msi file> {/L*v "<log file>} {/qn | /qr | /qb} {PROPERTY1="value1", PROPERTY2="value2", ...} where

/L*v -> optional. used to generate a verbose log file

/qn - no UI (quiet installation mode)

/qr - Reduced UI mode

/qb - Basic UI mode

PROPERTY variables are optional. If you want to customize the installation location, personalities installed, etc., you can use property variables. Values passed to these property variables should be enclosed within double quotes if the value contains a blank space.

The following properties are supported by the Borland Developer Studio 2006 setup program:

        Troubleshooting

DEBUG_MODE=ON (use this with /L*v option if you want to get the logs printed from custom code. used for troubleshooting)

        Destination locations

INSTALLDIR=<installdir>

BORLAND_SHARED_DIR=<borland shared dir>

BSBDE=<BDE install dir>

BSDBD=<Database Desktop dir>

        Third-party Add-ons

INSTALL_DEMEANOR

INSTALL_COMPONE

INSTALL_RAVE

INSTALL_NUNIT

INSTALL_CALIBER

Pass in a "1" to install the product, or put in an empty string ("") if you do not want to install it. If you don't pass in one of these properties, msi will launch the third-party setup scripts if the products are not already installed.

        Indy and Office Win32 package registration

INDY_VER=Indy10 (or) Indy9

MSOFFICE_VER=DelphiOfficeXP or DelphiOffice2k or BCBOfficeXP or BCBOffice2k

        Personality Selection

DELPHI_DOTNET_PERSONALITY

DELPHI_WIN32_PERSONALITY

CSHARP_PERSONALITY

BCB_PERSONALITY

Pass "1" to install the personality, "" if you do not want to install it. By default all personalities are installed.

        File Type Associations

ASSOC_DELPHIDOTNET

ASSOC_DELPHIWIN32

ASSOC_CSHARP

ASSOC_BCB

ASSOC_ASPDOTNET

ASSOC_BDS

Pass "1" to associate the file extensions, "" to not associate. By default all file types that belong to the selected personalities will be associated with BDS.

ASSOC_DELPHIDOTNET will associate files of extension : pas, dpr, dpk, nfm

ASSOC_DELPHIWIN32 will associate files of extension : pas, dpr, dpk, dpkw, dfm, rc

ASSOC_CSHARP will associate files of extension : cs

ASSOC_BCB will associate files of extension : cpp, hpp, h, bpr, bpk, bpf, rc ASSOC_ASPDOTNET will associate files of extension : aspx, ascx, ashx, asax, asmx, bdsdeploy ASSOC_BDS will associate files of extension : bdsgroup, bdsproj

        Example

msiexec.exe /I "C:\setup\BDS2006.msi" /L*v "C:\temp\install.log" /qn DEBUG_MODE=ON INSTALLDIR="C:\Borland\BDS\4.0" BSBDE="C:\BorShared\BDE" INSTALL_NUNIT=1 INSTALL_RAVE="" INDY_VER=Indy10 CSHARP_PERSONALITY=""

        Silent Uninstallation

To run a silent uninstallation (un-install from a command line without the use of a GUI wizard), type the following in a command window:

msiexec /x "<msi file>" {/L*v "log file"} {/qn | /qb | /qr} (or) if you don't have the .msi file, use the following syntax:

msiexec /x {7ED5371F-F4EA-48F9-B8F7-C8777AD9DF69} {/L*v "log file"} {/qn | /qb | /qr}

{7ED5371F-F4EA-48F9-B8F7-C8777AD9DF69} is the msi product code for Delphi Developer Studio 2006

/L*v is optional

/qn -> No UI or Quiet mode

/qb - Basic UI mode

/qr - Reduced UI mode

MSI Command-line Reference:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/command_line_options.asp

        Modifying the Installed Product Using Add/Remove Programs

Once the product is installed, you can add optional products, add/remove personalities and/or add/remove features. Use the Control Panel | Add/Remove Programs command, select the "Modify" button, and then choose personalities/features that you want to add or remove.

The feature selection dialog that you see in maintenance mode is different from the one that is displayed during initial installation. During initial installation, only the features that are part of the selected personalities will be displayed in the feature selection dialog. But in maintenance mode, all features will be displayed in the dialog.

For example, if you initially installed only the Delphi.NET personality, when you use the Modify command to include the "Delphi Win32" personality, you will see all of the Delphi Win32 features in the feature selection tree disabled by default. You have to select all of the Delphi Win32 features that you want to install and then click Next to continue with installation.

Note that if you select features that are not part of the selected personality, those features will not be installed even though you selected them in the feature selection dialog. For example, if you installed Delphi Win32 and C++Builder with all features selected during initial installation, and then you use the Modify command to remove C++Builder, the feature selection dialog will show all of the C++Builder features such as Corba and CodeGuard enabled by default. This is because these features are currently installed on your system. But when you uncheck the C++Builder personality while you were using the Modify command to un-install, all of those C++Builder features will be removed (even though it looks like they are enabled by default).

        Installing Optional, Add-on Products

        Borland CaliberRM SDK

Required for CaliberRM integration in Borland Developer Studio. This option enables CaliberRM users to add, remove, and update requirements for software projects within the Borland Developer Studio IDE and to create links between CaliberRM requirement specification and code.

        ComponentOne Studio Enterprise for Borland Developer Studio

Provides grid, reporting, charting, data, user-interface, and e-Commerce components for .NET and ASP.NET.

        Wise Owl Demeanor for .NET, Personal Edition

This option provides you with a .NET obfuscation tool that assists in protecting intellectual property by making it difficult to reverse engineer managed code applications and assemblies.

        Rave Reports Borland Edition (BE)

Rave Reports offers a powerful suite of Win32 and .NET components that simplify the task of creating professional reports.

        NUnit Unit Testing Framework

A unit-testing framework for all .NET languages that takes advantage of many .NET language features, such as custom attributes and other reflection-related capabilities.

        MDAC 2.8 SP1

Microsoft Data Access Components (MDAC) 2.8 SP1 contains core Data Access components such as the Microsoft SQL Server™ OLE DB provider and ODBC driver. This redistributable installer for the MDAC 2.8 SP1 release installs the same Data Access components as Microsoft Windows XP SP2. This release does not include Microsoft Jet, the Microsoft Jet OLE DB Provider or ODBC driver, the Desktop Database ODBC Drivers, or the Visual FoxPro ODBC Driver.

Operating Systems Supported by MDAC 2.8: Windows 2000; Windows 98; Windows ME; Windows NT. For details, please visit http://www.microsoft.com/downloads/details.aspx?familyid=78cac895-efc2-4f8e-a9e0-3a1afbd5922e&displaylang=en

        Known Installation Issues

If you modify the BDS 2006 installation by clicking the Change button in Add/Remove Programs and choosing the Modify option to remove personalities or features, setup will make the appropriate changes in the registry only in HKEY_LOCAL_MACHINE. Follow any one of the steps below to make these changes in HKEY_CURRENT_USER.

After doing a maintenance install from Add/Remove Programs, re-start the IDE and click on No for all the Package not found errors and Assembly not found errors. This will automatically remove the correct assembly or package entries from the registry and should prevent these errors when starting BDS 2006. This is the preferred option, since the options outlined below involve editing the registry.

Manually edit the HKEY_CURRENT_USER\Software\Borland\BDS\4.0\Known Assemblies, Known IDE Assemblies, Known IDE Packages and Known Packages registry keys to delete the assemblies or packages that were removed by the setup in HKEY_LOCAL_MACHINE\Software\Borland\BDS\4.0.

Delete the HKEY_CURRENT_USER\Software\Borland\BDS\4.0 registry key and re-start the IDE to get the updated registry settings. Be aware that when you delete this key, you will lose your customized settings that were stored under this registry key.

Note: Read the WARNING at the end of this file before editing your system registry.

Uninstalling BDS 2006 when an earlier version of BDS or C++Builder product installed:

If you have BDE installed from any earlier version of BDS or C++Builder Architect or Enterprise Edition that co-exists with BDS Architect or Enterprise Editions, Borland strongly recommends that you perform a back up of the idapi32.cfg file in your BDE directory (by default C:\Program Files\Common Files\Borland Shared\BDE) before uninstalling BDS. The BDS 2006 uninstallation removes some BDE files including idapi32.cfg and this causes all pre- configured BDE aliases to be removed after uninstallation. If you have performed a back up of idapi32.cfg, then you can restore the BDE aliases by renaming the back up copy to idapi32.cfg after BDS 2006 uninstallation. You may also have to repair the earlier version of the BDS 2006 or C++Builder product by using the Add/Remove Programs command to restore the other missing BDE files.

        Uninstalling This Product

To uninstall the product, the Administrator who initially installed the product must open the Control Panel, select Add or Remove Programs, select Borland BDS 2006 Architect Edition and click the Remove button. After uninstalling, in order to remove user-specific data from the Windows registry, all non- Administrator users of the product must log in and delete the following registry key:

HKEY_CURRENT_USER\Software\Borland\BDS\4.0

WARNING: Registry editing is performed at your own risk. This document and other documentation that accompanies this product describe how to edit your Windows registry. In most cases, Borland recommends that you use the Microsoft Regedit tool to perform editing. Whatever tool you use, however, you should, before making any changes, make backups of your registry and thoroughly familiarize yourself with the editing tool and the registry editing process. The registry is a critical component of your operating system, and any mistakes you make while editing it can cause your machine to stop functioning.



Server Response from: ETNASC03