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.

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

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.#*.

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.

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.

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:

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.