Borland 7
.NET version of TeeChart Standard will be available at the Steema Web site at http www.steema.com . From the Win32 tab, all components appear in VCL for .NET. Missing from the System tab are OleContainer, DdeClientConv, DdeClientltem, DdeServerConv, and DdeServerltem components. Even the Win 3.1 tab from VCL is present in VCL for .NET, with the exception of the TDBLookupList and TDBLookupCombo components. Finally, the Dialogs tab is completely present in VCL for .NET. Based on these components,...
Borland 4
Delphi 7 can help you prepare Win32 applications for .NET, with a set of three new warnings. Because they are disabled by default, they must be explicitly turned on using the Project Options - Compiler Warnings tab. The new set consists of warnings for unsafe types, unsafe code, and unsafe typecasts. You can either enable these warnings in project options, or the preferred approach specify them at the top of source files as follows WARN UNSAFE_TYPE ON WARN UNSAFE_CODE ON WARN UNSAFE_CAST ON You...
Borland 11
Many new powerful technologies in the Microsoft .NET Framework are available to developers. Some of these, such as ADO.NET, make current Win32 technologies either unnecessary or obsolete. This section describes the data access technologies offered by Delphi 7 and explains whether and how they are available to use in VCL for .NET applications with Delphi for .NET. The following table gives an overview of the available data access technologies in Delphi 7, and lists the VCL for .NET counterparts...
Borland 9
Figure 3 Convertit sample application for .NET AppEvents Let's end the VCL sample applications with a more complex application in the Delphi7 Demos AppEvents directory. Again, this sample application works as expected when loaded in the Delphi for .NET IDE and run as a native .NET application Figure 4 . Figure 3 Convertit sample application for .NET AppEvents Let's end the VCL sample applications with a more complex application in the Delphi7 Demos AppEvents directory. Again, this sample...
Borland 10
Before we move on to sample applications with database support, let's look at deployment of a Delphi for .NET application specifically, a VCL for .NET application. If we take the last sample application, and look inside the Project Manager, the reference node of the project lists only the System.Drawing.dll assembly. This is the only assembly the AppEvents sample application for .NET requires. All VCL for .NET units are compiled into the executable, which as a consequence is about 1.5 MB. On...
Borland 5
As a consequence of using the unsafe keyword, the resulting application or package no longer passes PEVerify2. However, the unsafe keyword helps you with a first migration of unsafe sections , which you can later rewrite using native safe .NET code. Delphi for .NET has also introduced several new or extended language features to enhance the way it conforms to the .NET standard, such as sealed classes, final methods, and strict private and protected access specifiers. In order to avoid existing...
Borland 6
Most Delphi 7 VCL components appear in the VCL for .NET component set that is included with Delphi for .NET. The Component Palette is replaced by the Tool Palette, but similar categories exist Standard, Additional, Win32, System, Win 3.1, Dialogs, Data Access, Data Controls, dbExpress, DataSnap, BDE, InterBase, InterBase Admin, Indy Clients, Indy I O Handlers, Indy Intercepts, and Indy Misc see Figure 1 . Figure 1. Delphi for .NETIDE with VCL for .NET component categories Figure 1. Delphi for...
Borland 12
One category of VCL components that wasn't migrated to VCL for .NET is the Decision Cube. Because the source code is included with Delphi 7 at least in the Enterprise edition , you can attempt to migrate these components yourself if you desperately need them In the Data Access category, the TXMLTransform, TXMLTransformProvider, and TXMLTransformClient components are not included with Delphi for .NET. Support for XML in .NET can be found in the System.Xml namespace. The Data Controls category is...