Как установить borland developer studio 2006 на windows 10

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

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:

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:tempbds2006_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:tempbds2006_arch_upd2.msp» /L*v «C:tempbds2006upd2.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:tempbds2006_arch_upd2.msp” /L*v “C:tempbds2006_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_MACHINESOFTWAREBORLANDBDS4.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.

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

    General

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

    C++

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));

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));

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

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

    Compiler

#include <vcl.h>

#pragma hdrstop

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

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

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

    ECO

public
    function AsIObject: IObjectInstance;

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

    IDE

    .NET/BDE

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.1 Distributing Custom Assemblies and Packages

    2.2 Borland Runtime Assemblies and Packages

    2.3 Runtime Assemblies and Packages

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 FilesCommon FilesBorland SharedImages

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:InetpubScripts. 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 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.

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.

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.

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.

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

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.) 

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 InfoStarTeam 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.

    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

    Silent Installation

    Troubleshooting

    Destination locations

    Third-party Add-ons

    Indy and Office Win32 package registration

    Personality Selection

    File Type Associations

    Example

    Silent Uninstallation

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).

    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

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_USERSoftwareBorlandBDS4.0Known 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_MACHINESoftwareBorlandBDS4.0.

Delete the HKEY_CURRENT_USERSoftwareBorlandBDS4.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 FilesCommon FilesBorland SharedBDE) 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.

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_USERSoftwareBorlandBDS4.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.