delphi2006不支持x64
2006: “Delphi Highlander”
The “Highlander” release will focus on updating the entire Delphi toolset to support .NET 2.0. There will be ongoing work for Win32 Delphi and Win32 C++ (such as unit testing and additional refactorings) but the most of the new work in Highlander will be focused on .NET 2.0. Highlander will add Delphi.NET support for generic types, partial classes, and nullable types, and all WinForms, Web Services, and ADO.NET support will be converted to support .NET 2.0. VCL, BDP, and ECO will all support .NET 2.0 as transparently as possible to minimize migration issues for customers. Delphi Highlander will fully support existing Delphi projects, including existing ASP.NET projects, and will provide seamless project conversion to .NET 2.0.
Highlander will include IDE design surfaces for .NET Compact Frameworks (using VCL.NET on CF), as well as support for transparently developing and debugging 64 bit .NET apps written using WinForms and VCL.NET. In addition, 64 bit code generation will be added to the Delphi native code compliers to support native 64 bit development and debugging. The phased approach to Unicode will continue in Highlander and through the subsequent Longhorn release, with enhancements to both the IDE and VCL runtimes to support Unicode.
The current plan is to release Highlander in calendar year 2006, with tech preview builds available for download by registered Delphi customers shortly after .NET 2.0 is released.
2007: “Delphi Longhorn”
While the transition from .NET 1.x to .NET 2.0 is non-trivial, the next-generation presentation and communication technologies (“Avalon” and “Indigo” respectively) that Microsoft plans for their Longhorn release constitute far more drastic changes for Windows developers, who may face challenges reminiscent of the VB to VB.NET transition. The Delphi release that follows Highlander will help reduce migration issues by providing a VCL for Avalon and by integrating Indigo into Delphi’s cross-tier communications framework (e.g. ECO, BDP, DataHub and DataSync). In particular, support for reverse-engineering of existing applications with Together and deployment of executable models with ECO for Indigo will significantly reduce the complexity of porting existing applications. In addition to supporting Longhorn, Avalon, Indigo, and the WinFX APIs from Microsoft, this release will introduce managed C++ support as well as ECO support for C++, and will continue to add and enhance productivity features applicable across all language personalities and platforms in the studio.