Thank you for choosing Delphi Prism™, the next generation Delphi development solution for .NET and Mono™, the cross platform, open source .NET framework.

This file contains important supplementary information that might not appear in the main product documentation. CodeGear recommends that you read this file in its entirety. For an updated version of these Release Notes, see the CodeGear Developer Network article ( http://dn.codegear.com/article/38971).

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

Updated versions of both the Readme and Install files are also available on the documentation wiki at http://prismwiki.codegear.com.

Keep up to date with the latest developments on the Delphi Prism product homepage at http://www.codegear.com/delphi/prism.

Before installing, uninstalling, or upgrading the product, see the INSTALL and LICENSE files for detailed information about installation and licensing issues. After installation, the default location of these files is C:\Program Files\CodeGear\Delphi Prism.

Also see the INSTALL file for information on uninstalling the product.

Make sure that your subscription stays active to guarantee continued access to the latest releases so that you have the most recent fixes and new features available.

Delphi Prism officially supports the Microsoft .NET Framework 1.1, 2.0, 3.0 and 3.5, the Microsoft .NET Compact Framework 1.0 and 2.0, as well as Mono.

It has been tested with .NET 2.0 and above for compatibility with both 32 and 64 bit.

The matching Framework SDK should be installed to use Delphi Prism with the respective versions of the Microsoft .NET CLR.

Supported and Tested Platforms are:

• Microsoft .NET Framework 3.5 (LINQ)
• Microsoft .NET Framework 3.0 (WPF and WCF)
• Microsoft .NET Framework 2.0, with and without SP1
• Microsoft .NET Framework 1.1, with and without SP1 (legacy only)
• Microsoft .NET Compact Framework 2.0
• Microsoft .NET Compact Framework 1.0, with and without SP1 and SP2 (legacy only)
• Mono 2.0

    Visual Studio 2008 and .NET 3.5

Delphi Prism will continue to improve and these improvements will be available to you as part of your ongoing subscription. Make sure that your subscription stays active to guarantee continued access to the latest releases so that you have the most recent fixes and new features.

Peer-to-peer support for Delphi Prism is available via our newsgroups and forums at https://forums.codegear.com.

Check out the documentation wiki at http://prismwiki.codegear.com to get started with Delphi Prism.

    Sample Projects

• Cannot update values on ASP.NET form with SqlDataSource and GridView controls

  For instance, if you connect a GridView and an SqlDataSource control to a database and enable editing, you might not be able to update data. This problem can occur when the SqlDataSource control has generated an UPDATE statement with the wrong number of parameters. If editing is not working, check the Update SQL statement and parameters. This problem can also occur when the GridView's DataKeyNames property is not set correctly. The GridView.DataKeyNames property should include the name of the primary key.

• Optimistic concurrency is not fully supported for tables that allow null values

  Optimistic concurrency is not fully supported with Blackfish SQL and InterBase for tables with colums that allow null values. Rows with null values may not be able to be updated or deleted. To turn off optimistic concurrency, use the checkbox in the SQL Datasource Wizard Advanced Options.

• Declaring a class before the MainForm class breaks the project

  For instance, create a new Windows Application, add a button, and double-click the button. In the code editor window, add a new class above the form declaration in the type section. When you click the [Design] tab, you get an error message and the design area is not displayed. You cannot access the design area until you remove the class definition.

• Cannot create a datasource for MS SQL with Visual Studio Shell

  If you get an error while adding a datasource, a workaround is to install the following service pack:

  Microsoft SQL Server Compact 3.5 Service Pack 1 and Synchronization Services for ADO.NET version 1.0 Service Pack 1 for Windows Desktop
  http://www.microsoft.com/downloads/details.aspx?FamilyID=dc614aee-7e1c-4881-9c32-3a6ce53384d9&displaylang=en

• Database connections seem to persist after uninstalling Feature Pack

  If you uninstall the Feature Pack when a database connection exists and terminate Visual Studio, when you restart Visual Studio, the connection appears to still exist. However, the connection is not functional. If you attempt to expand it, you get an error. You also get an error if you attempt to create another connection, which is as designed since the Feature Pack contains the database support.

  To workaround this problem, remove the connection by right-clicking the connection in Server Explorer and click the Delete menu item. Also, if you delete all connections before uninstalling the Feature Pack, you won't see this problem.
  

• Uninstalling Delphi and C++Builder 2009 after installing Delphi Prism shuts down Blackfish service

  If you install Delphi Prism, then uninstall Delphi and C++Builder 2009, Blackfish service gets shut down. You need to manually restart Blackfish service. The executable for the Blackfish server is BSQLServer.exe.

• Sync editing method name containing International characters corrupts method name

  If you create a method with International characters, right-click the editing pane and click Complete Class to create the method implementation, then use Sync editing to change the method name, the resulting method name in the implementation section is incorrect.

  The DXCore extensibility framework can be added to Delphi Prism and adds a sync editing feature. This framework is developed by Developer Express Inc. and can be used free of charge for personal use. DXCore can be downloaded at http://www.devexpress.com/Downloads/Visual_Studio_Add-in/DXCore.

• Installing Delphi Prism overwrites Delphi 2007 files

  If you have Delphi 2007 installed, installing the Delphi Prism Feature Pack overwrites the files dbxconnections.ini and dbxdrivers.ini with the 12.0 version of dbExpress drivers. If you uninstall the Delphi Prism Feature Pack, the uninstaller does not restore a backup of dbxdrivers.ini and dbxconnections.ini with 11.5 driver versions, but just removes all 12.0 drivers.

• Uninstall of Delphi 2009 is incorrect on a German system after installing Delphi Prism

  If Delphi 2009 and C++Builder 2009 are installed on a German system, Delphi Prism can be installed on the system, but uninstalling Delphi 2009 and C++Builder 2009 causes errors. The install of VS Shell removes a pre-requisite installed by Delphi 2009 and C++Builder 2009 (the Microsfot .NET 2.0 German Language Pack). When uninstalling, the Delphi and C++Builder 2009 uninstaller looks for this Language Pack and generates an error. The workaround is to re-install the .NET language pack.

• TeeChart demo fails with several errors

  If you load and build \Samples\Third Party\TeeChart, you get a series of errors, such as: "Error 2 (PE17) Namespace "Steema.TeeChart.Styles" does not exist or has no public types."

• You must programmatically assign the DataMember property of a BindingSource for tables that contain International character fieldnames

  For example, if a table in a Blackfish SQL or MSSQL database contains International characters, adding the data to a DataGridView on a Windows Form causes an error that can crash Visual Studio. This problem occurs only if you add the data source by using the task dropdown combo box for the DataGridView component. The BindingSource component cannot be linked to any tables that contain International character fieldnames by using the Properties window. The BindingSource component must be set programmatically in the Source page (such as bindingSource1.DataMember:= 'tableName';), which then gets updated and reflected on the Design tab. This problem does not occur if the table is dropped from the data source window.

• A typed dataset created in the Dataset Designer might not display data in the DataGridView when dropped onto the Design pane

  If you drag a typed dataset from the DataSource pane to the Design pane and the grid appears to be blank, the reason is that the BindingSource cannot link to the DataSet table with the DataMember property. There are two workarounds:

  • Close and reload the project; the DataMember property will now show the table from the dataset to be linked.

  • Alternatively, use the Data | Add data source command to automatically generate the correctly linked BindingSource and DataGridView components.

• The Windows/WPF template is not supported by the Add New Data Source wizard.

  The Add | New Data Source wizard allows you to add a database and a data connection for a Windows/WPF project, but the wizard does not complete.

• Cocoa application with NSTextField terminates if Control pressed with any key

  If you run a Cocoa application with a NSTextField component, pressing the Control key and any other key simultaneously aborts the application after about 5 seconds. This is a problem in Mono.

• Adding database connection to Blackfish SQL in Delphi and C++Builder 2009 fails on German system after uninstalling Delphi Prism

  If you install CodeGear Delphi and C++Builder 2009 on a German system, then install and uninstall Delphi Prism, you can't connect to Blackfish SQL. You can work around this by adding and starting the Blackfish SQL service bsqlserver.exe.

• To avoid problems with overlong project path names, change the default VS project location

  If fully qualified references (project pathname and project name) exceed the Microsoft limit of 260 characters, you might not be able to create the project or reopen it after saving. The recommended workaround is to set a much shorter default location for projects.

  To do this, navigate to Tools | Options | Projects & Solutions. For Projects location, either enter a short pathname such as C:\Projects or click Browse and select a high-level folder as the default project location.

• ASP.NET designer not going to correct code in editor

  In an ASP.NET project, double clicking a component on the design tab or clicking Event Handler in Properties event may not place the cursor in the correct handler code in code editor.

• Only one connection allowed for Blackfish local database

  Allowing only one connection for a local Blackfish database has development ramifications. For instance, if you have the connection open in Server Explorer, then run your application, you get errors if it tries to connect to the database. Close the connection in Server Explorer before running the application.

  This restriction is documented in the Blackfish Developers Guide at http://docs.codegear.com/docs/radstudio/radstudio2007/RS2007_helpupdates/HUpdate4/EN/html/bfsql/connections_xml.html

  "Local connections access the Blackfish SQL database engine in-process. This provides improved performance over a remote driver, but requires that the Blackfish SQL engine be present and running in the same process as the application. Several simultaneous local connections created in the same process can connect to a database. However, only one process can have a database file open at a time. Consequently, while a process has a database file open, it becomes the only process that can connect to that database over a local connection."

• DataSnap entry appears in Delphi and C++Builder 2009 Data Explorer

  After you install Delphi Prism, DataSnap appears in the provider list in Data Explorer for Delphi and C++Builder 2009 even though DataSnap is not supported in Data Explorer. This occurs because there is a [DataSnap] entry in the dbxdrivers.ini file:

  [DataSnap]
  DriverUnit=DBXDataSnap
  DriverAssemblyLoader=Borland.Data.TDBXClientDriverLoader,Borland.Data.DbxClientDriver,Version=12.0.0.0,Culture=neutral,PublicKeyToken=91d62ebb5b0d1b1b
  Port=211
  

  This entry is not needed for Delphi Prism and may be removed, which removes the DataSnap entry in Data Explorer. If you do modify this file, you should make sure you remove only the lines of this entry, since you could cause the product to not function properly otherwise. In particular, do not remove the DataSnap=1 entry elsewhere in dbxdrivers.ini.

Documentation is provided on a wiki at http://prismwiki.codegear.com. The wiki allows you to easily enhance information on topics. We welcome your feedback.

Since documentation is on a wiki, it is constantly expanded and updated. A snapshot of the documentation is also installed with the product for access when your computer is not connected to the Internet. You can access either the installed or online version via the Help menu.

You can also get a snapshot of the latest documentation at any time on the wiki.

Delphi Prism supports ADO.NET and ASP.NET development.

Delphi Prism includes several databases.

    Blackfish SQL

    InterBase 2009 SMP Developer Edition

    DataSnap