Embarcadero is to release Delphi for .NET as a Visual Studio add-on, called Prism. Marco Cantu has a summary. Note that according to this post, which is based on an
announcement statement by product manager Nick Hodges at the SDN conference near Amsterdam, there will be:
full support for the .NET framework 3.5 (WinForms, WFP, Silverlight, ASP.NET, WCF, LINQ) … CodeGear will provide Datasnap 2009 integration and dbExpress for ADO.NET support
It looks as if this will be a full alternative language for .NET developers. Note that many of the language changes, such as generics, in the Win32 version of Delphi 2009 seemed to have .NET compatibility in mind. It makes sense for Embarcadero to use Visual Studio to host .NET development tools, just as it uses Eclipse for Java.
There remains an awkward question. What advantage is there in using Delphi (a version of Pascal) rather than C# for .NET development? If this is aimed only at existing Delphi developers migrating code, it will only ever be a niche.
I am trying to clarify a couple of points. To what extent, if at all, will Prism support the .NET version of Delphi’s VCL (Visual Component Library), which would not fit smoothly with the Visual Studio design tools? Even if VCL.NET applications work, you would probably be better off using Delphi’s own IDE for them. Code ported from Win32 Delphi will likely use the VCL, so this is tough to get right. And what is the future of Delphi for .NET in RAD Studio? I will update this post when I know more.
*Comments below suggest that this is in fact Oxygene rebadged; I won’t say more until I’ve got official confirmation.
- No more Delphi for .NET: Prism removed from RAD Studio XE4
- Oxygene for Java released: develop for Android and Java runtime with Delphi language in Visual Studio
- Visual Studio Code: an official Microsoft IDE for Mac, Windows, Linux
- Changes in the Delphi language for ARM and mobile support
- Xamarin 3.0 brings iOS visual design to Visual Studio, cross-platform XAML, F#, NuGet and more