Borland Developer Studio 2006, Update 1 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. This file only includes information about what has changed in the product since Borland Developer Studio 2006 was released. This update completes the functionality of the Preview Technology for C++ and C in Borland Developer Studio 2006. For information about the original release of Borland Developer Studio 2006, see the Readme file. This information may not appear in the main product documentation. Borland recommends that you read this file in its entirety.

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 removed after it is installed if you have MSI 3.0 or above. However, there is a known issue that MSI will prompt for the source media disks during uninstallation of Update 1. You should insert the disk that is being prompted for to continue with uninstallation. You will not see this problem if you did not install BDE.

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_upd1.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_upd1.msp" REINSTALL=ALL REINSTALLMODE=omus will install the update.

The following example will also generate a log file named bds2006upd1.log under C:\temp
msiexec.exe /p "C:\temp\bds2006_arch_upd1.msp" /L*v "C:\temp\bds2006upd1.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_upd1.msp” /L*v “C:\temp\bds2006_arch_upd1.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.1.

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.1 and 1, respectively.

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

Resolved Defects

The following issues, listed in the Known Issues section of the Readme file for the original release of Borland Developer Studio 2006, have been resolved in this update. Information on additional resolved issues is available through Borland Quality Central.

Description
A new dbexpasa30.dll driver is being delivered in this update which will fix a problem with stored procedures returning NULL for some parameter types.
If you are creating a C++ Package that contains a Delphi unit that uses the DesignIntf and DesignEditors tools, you had to choose `Project\|Options\|Pascal` `Compiler\|Other` Options and then add `-LUDesignIDE` for the compiler to work correctly. Now the DesignIntf and DesignEditors tools are supported by the compiler.
The dialog for specifying C++ build events accepts the names of batch files as well as batch syntax. However, the batch syntax created a separate process for each line in the dialog. Commands relying on the value of one or more environment variables, set in previous commands, didn't always work correctly. For example, the following command failed because OUTPUT_DIR was no longer associated with the set command: set OUTPUT_DIR=c:\project\bin copy *.exe %OUTPUT_DIR% Now the batch syntax creates a single process.
The project manager now supports moving a file outside of its parent directory in order to change the build order. Previously, you could change the build order only by moving files around within a directory, or by moving directories within the project. For example, if you had 2 files in Dir1 and 2 files in Dir2, the project manager did not support the following build order: Dir1/file1 Dir2/file1 Dir1/file2 Dir2/file2
The debugger/module view now shows symbol files for modules with .tds files.
The context menu of .rc files in the Project Manager did not contain the Compile Action option. This was because renamed .txt files were not placed in the proper container with the associated functions. Now the .txt files are placed in the proper container.
Rename Refactoring had known problems when trying to rename components that were managed by the VCL designer. The refactoring could generate errors or fail to rename all references. You can now use Rename Refactoring to rename components that are managed by the VCL designer.
You can now perform Rename Refactoring on a single instance of a char variable.
Now the C++ personality supports dropping Microsoft Office components onto a Form. In the past, after dropping Microsoft Office components onto a Form, building the project caused the following C++ fatal error: "Word_XP_srvr.h(1989): F1008 Out of memory"
Exporting projects to a makefile is now supported.
In previous releases, the IDE did not allow the user to make changes to the Project_TLB.h file. As soon as the unit was saved, the IDE would refresh the Type Library immediately, thus overwriting the Project_TLB files with auto-generated code and losing all manual changes. This has been fixed with a new check box on the type library editor toolbar that is called "Auto Refresh". If unchecked, you must click the Refresh button to have the _TLB.pas and _TLB.cpp/h files regenerated with the type library updates. The box is checked by default, and the state of the checkbox will persist between IDE sessions and projects.
The Project \| Build Configurations menu will bring up the Build Configuration Manager dialog. This dialog allows changing the active build configuration for multiple projects simultaneously. The "Configuration Name" combo box shows available build configurations for all projects in the current project group; when a configuration is selected all the projects with a same-named configuration are displayed in the list view along with the name of their currently active configuration(s). Select one or more projects in the list view then click "Apply" to apply the selected configuration to the selected projects. Note that the "Edit" button is not active unless one and only one project is selected - multiple build configurations cannot be edited simultaneously.
Previously, compiling an ActiveX library with an Active Form set to "Include About Box" could result in errors. This has been resolved.

Known Issues

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

C++

The following C++ Rename refactorings are not supported:
1. Refactoring inside template definitions.
2. Refactoring inside macro definitions.
C++ Rename refactoring has the following known issues:
1. Template instantiations and the primary template aren't recognized as references of each other.
2. Template specializations and the primary template aren't recognized as references of each other.
3. Unable to rename Free() in a Delphi class.
4. Parameters of qualified types can't be refactored.
The refactoring engine fails if you attempt to rename a class name from a header file that is not part of a project but is getting included.
Rename Refactoring may report a compilation error in VCL console applications when the code does not explicitly include the appropriate header files for the VCL components that are being used. The workaround is to include the .hpp file which contains the declaration of the VCL components.
Only one instance of Rename Refactoring should be active at any given time. After Rename Refactoring has been invoked, a background thread will begin searching your project for references to the symbol. Do not start another instance of Rename Refactoring until this first instance has been applied or canceled.
In this release, an overloaded version of Synchronize was added to the TThread class. Due to a limitation in the C++ compiler, this can result in applications that use the Synchronize method in their C++ code no longer compiling. If you use the Synchronize method as follows, you will now get a compilation error: Synchronize(MySynchronizationFunction); To work around this issue, add an & to the name of the function used as a parameter to Synchronize: Synchronize(&MySynchronizationFunction);
If you have installed Borland Developer Studio 2006 on the same computer that contains a version of C++Builder 6 is installed, make sure BDS\bin is before C++Builder in the search path. Otherwise, you may see the error, vclshmem.cpp: GetBorMemPtrs failed.
Invoking Rename Refactoring on a variable of type "TForm? *" is not supported in this release. Doing so will generate an error message in the refactoring view. However, the refactoring will still be enabled and if you choose to execute it, you will have to manually change the USEFORM macro in your project's main .cpp file.
There is a known issue when using Rename Refactoring to change the name of a nested class. The implementation of the nested class's destructor will not be properly renamed.
Components written using the C++ personality in BDS2006 are not available to the Delphi personality.
Rename Refactoring can be used to change the name of a TForm-derived class. If you undo this refactoring, you may see errors indicating that the IDE could not find the class name. This can be corrected by saving, closing and re-opening the project.
In this release, Rename Refactoring is not supported from within a header file that is not part of an IDE-managed unit (that is, the header file does not appear in the tabs along the bottom of the code editor).
You can not redo a refactoring that has been undone. To redo a refactoring, you have to remove the old refactoring from the preview window and start a new refactoring.
In rare cases, unfolding will fail on code where multiple fold regions start on the same line. This will give the appearance that much of the code has disappeared. To correct this state, right-click in the Code Editor and choose "Unfold All" or close and reopen the file.
Header file dependencies are not automatically created under .c / .cpp files in the project manager due to negative performance impact with medium to large size projects. To see the header files a .c / .cpp file is dependent on, right click on that file in the project manager and select "Show Dependencies" (NOTE: dependency information is not available until a file is compiled).
If you install this Update and also have Indy 9 installed, you will need to add the following entry to the Tools | Options | C++ Options | Paths and Directories | Search Path edit box: $(BDS)\include\indy9, before you can use Indy 9 with the C++ personality.
Indy 10 is not ready to use with C++ at this time. An updated version of Indy 10 for C++Builder will be posted on the Indy web site and the Borland Developer Studio registered user's page when it becomes available.
When a C++ package is installed in the IDE, certain properties in the object inspector may be displayed with in C++ syntax. For instance, component field properties normally appearing as "Component.FieldName" will instead appear as "Component->FieldName", and boolean properties will appear in all lower case. This is a known issue which does not affect functionality.
In the C++ personality, internal compiler errors may result if cached pre-compiled headers become corrupt. Workaround: Delete your pre-compiled headers and restart the IDE. By default, these files are vcl100.csm and vcl100.#01 (incrementing as necessary) and are located in $(BDS)\lib.

Copyright © 2005 Borland Software Corporation. All Borland brand and product names are trademarks or registered trademarks of Borland Software Corporation in the United States and other countries. All other marks are the property of their respective owners.