What is Not in the Delphi Roadmap
As you’ve hopefully noticed, we’ve recently published and then updated our Delphi/C++Builder Roadmap. We hope it is useful to you and that you are able to see where we are headed and what we consider important going forward.
However, careful readers of the roadmap will notice not only what is on the roadmap, but also what is not on the roadmap. Two things that are not on the roadmap are a full-featured personality for C# and support for WinForms.
In Highlander, C# support will be pretty much what the VB.NET level of support has been — open, edit, syntax highlight, compile and debug. We decided to do this for several reasons. The main reason was resources — providing full C# support would take a pretty significant chunk of development time — time that would not be time spent on Delphi itself and the VCL. We would much rather spend our effort supporting Delphi developers than supporting C# developers. Delphi support is vastly more important to our customers than C# design-time support, so we decided to put our efforts into supporting Delphi developers. (You’ll still be able to include C# code in your projects, however — you just won’t be able to design with it.)
WinForms support was much the same — it would take a significant amount of effort to support WinForms development in RAD Studio, and that would be development time taken away from the VCL and our own IDE. We’d rather spend our time supporting VCL developers than WinForms developers. In addition, we feel that the VCL is a vastly superior solution for desktop application development, both in Win32 and on .Net, and so we want to put our efforts into developing better solutions for that that superior framework. All that, combined with the unclear future of WinForms, led us to decide to stop supporting WinForms in our IDE.
Michael Dell has been quoted as saying "It’s easy to figure out what to do; it’s hard to figure out what not to do." I agree — making these decisions was hard. In making these decisions, we feel like we’ve made the tough choices of what to do, and the even tougher choices of what not to do. Going forward, we are committed to the VCL, to the Delphi language, and to the technologies that we develop that are supported by those to things. By marshaling our resources and focusing on Delphi and the VCL, we plan on bringing Delphi developers forward by enabling them to build the solutions that they need, not by simply supporting a laundry list of new technologies.
I find it unbelievable that it took you guys so many years to finally state that the VCL is "vastly superior to WinForms, both in Win32 and .NET" as opposed to saying that VCL.NET was just a transitional tool to help Delphi customers migrate to .NET. So much harm has been done to Delphi…
July 16th, 2007 at 2:30 pmTwo things:
- JED’s CF Build Helper plugin wont work anymore (I think). Which is really sad when there are no CF product scheduled in the roadmap for a very long time.
- Customers already migrated from Delphi cant be brought back with arguments like "Update your CodeGear product and do your old Delphi projects and your new C# in the same product". The last is an argument I’ve used a lot when selling in upgrades of Delphi to companies that decided they want to do the MS track but realize that they have a hard time leaving Delphi for all those old products that still need some maintenance.
July 16th, 2007 at 2:50 pmNick,
It’s my understanding that the most recent Delphi IDE is written using Delphi and is dependant upon the the .Net framework…
Was the IDE implemented using Winforms or VCL.NET?
Very curious.
Rick.
July 16th, 2007 at 2:55 pmRick —
The IDE is implemented using almost all VCL for Win32. There is a /very/ little bit of WInforms in the IDE, and we are migrating away from it.
Nick
July 16th, 2007 at 3:01 pmThe positive side I think is that C# personality was good for proving that Delphi could evolve at any level, same thing for CLX. Now lets make Delphi really take its own advantage, to stand on its own, and bring it to new levels of maturity.
Make it enterprise ready.
As an active user I was pleased with Delphi exploring such fields, but now, please, do never forget about the lessons learned. Thanks for the wise decisions.
Thanks for the wise decisions.
"…Delphi IS the VCL" - Marco Cantu
July 16th, 2007 at 3:16 pmI welcome this small bit of sanity as it gives CodeGear a chance to refocus some of its efforts and resources on the product that built the compnay - Delphi.
Is it safe to assume that this is tantamount to announcing that C#Builder has been retired with Kylix? (Or did I miss that announcement already?)
July 16th, 2007 at 4:00 pmDear CodeGear,
Years before you was saying that no more Win32 and let’s go into .NET.
People started using .NET with C# because it was more stable that Delphi.NET.
Now you see you cannot compete with MS and just cut off your C# developers the same way as you did it years ago with Win32.
People have lots of projects in C#. Now they should throw all that away…
Thousands of good components are available for WinForms, ASP.NET, .NET 3.5!
Ones for VCL.NET…
The same time .NET developers are still sticked with .NET 1.1 only. We even don’t see .NET 2.0 still.
What’s next?
We cannot rely on Borland/CodeGear (or whatever it is now) because you are unpredictable.
All that is just disappointing.
July 16th, 2007 at 5:32 pmonce upon a time, a $49.99 product, tp (turbo pascal) literaly erased ms pascal from the face of the earth. what made that possible? 3 things
1. innovation
2. innovation
3. innovation
i know, it sounds like "location, location, location"… but it’s true!
what it takes to do that? well, it would be easier for me to tell you what innvation is incompatible with! by now, you probably guessed, but, just to make sure, here is a $0.02 list:
1. nepotism (area owners, promotions, etc)
2. technically aliterates managers (literaly parasites, on different levels) - oh, i almost forgot, there is a twin ingredient to this… it’s called gread…
3. marketing blindness (directly realated to pct 1 & 2, but going beyond those two)
nick, you must know by know (after almost a whole year "inside") what i am talking about, not that i am implying anything…
time will tell, very soon, very very soon
all the best to everyone!
July 16th, 2007 at 6:15 pm…
once upon a time, a $49.99 product, tp (turbo pascal) literaly erased ms pascal from the face of the earth. what made that possible? 3 things
1. innovation
2. innovation
3. innovation
i know, it sounds like "location, location, location"… but it’s true!
what it takes to do that? well, it would be easier for me to tell you what innvation is incompatible with! by now, you probably guessed, but, just to make sure, here is a $0.02 list:
1. nepotism (area owners, promotions, etc)
2. technically aliterates managers (literaly parasites, on different levels) - oh, i almost forgot, there is a twin ingredient to this… it’s called gread…
3. marketing blindness (directly realated to pct 1 & 2, but going beyond those two)
nick, you must know by know (after almost a whole year "inside") what i am talking about, not that i am implying anything…
time will tell, very soon, very very soon
all the best to everyone!
July 16th, 2007 at 6:16 pm…
once upon a time, a $49.99 product, tp (turbo pascal) literaly erased ms pascal from the face of the earth. what made that possible? 3 things
1. innovation
2. innovation
3. innovation
i know, it sounds like "location, location, location"… but it’s true!
what it takes to do that? well, it would be easier for me to tell you what innvation is incompatible with! by now, you probably guessed, but, just to make sure, here is a $0.02 list:
1. nepotism (area owners, promotions, etc)
2. technically aliterates managers (literaly parasites, on different levels) - oh, i almost forgot, there is a twin ingredient to this… it’s called gread…
3. marketing blindness (directly realated to pct 1 & 2, but going beyond those two)
nick, you must know by know (after almost a whole year "inside") what i am talking about, not that i am implying anything…
time will tell, very soon, very very soon
all the best to everyone!
July 16th, 2007 at 6:16 pm…
While you are doing the right thing in going for Delphi vcl.net & win32,not giving priority to CF is a bad decision.
July 16th, 2007 at 6:48 pmIf only you cab squeeze in CF also some how,
I have no cause for complaint
Excellent decision!!! .Net developers should use the naitive tool provided by Microsoft. It has never made sense to me why a .Net developer would not use the tool suited for the job. Microsoft has so much planned for .Net that it would be next to impossible for you to stay current. I personally believe that too much is planned for that platform anyway. They are already talking about the next two versions of Visual Studio without any firm rlease dates. Time will show that MS is moving in the wrond direction. Their focus is strictly on large team corporate development. They have no interest in being the "spinach" because it does not sell additional products in their stack. Their biggest mistake will prove to be separating the interface from the code layer. Delphi has always been a better product! It’s a shame that such a good product was being limited by support for a competitor’s product line. Wait until they are finished and then take a look at supporting it. That should be some time in the next 5-7 years!
July 16th, 2007 at 7:16 pmI hear people lamenting the death of C#Builder while confirming the reasons it failed (CodeGear can’t compete), and then I hear people talking about CF and I really gotta wonder what the heck people are thinking.
Is CF even relevant anymore? If CodeGear released a CF product in a year, how many people would actually need it? More to the point, when the products written with that product get released, is CF even going to be around? MS is pushing towards lower power wintel powered devices with full versions of windows - how much longer does CF really have to live I wonder - 3, 4 years?
July 16th, 2007 at 10:51 pmNow this is the best decision taken by CodeGear for Delphi for a while.
Congratulations for the decision. You guys will now start to innovate where your expertise resides.
July 16th, 2007 at 11:23 pmCF is important not only to compile for pocketPC, SmartPhone powered by Windows CE but for Symbian too for example, in native way and with RAD. There is no ide that make this! Lazarus is too young.
July 16th, 2007 at 11:44 pmWhat about ASP.NET support Nick? What languages are supported for ASP.NET development and to what extent?
July 17th, 2007 at 12:04 amGreat decisions, If I were to offer a suggestion, I would even cancel VCL.NET and ASP.NET and replace them with ways of implementing interoperation between .NET and Delphi… i want to be able to add VCL, ActiveX, and .NET components in my native win32/64 Delphi. My app would only require .NET if I used any .NET components.
July 17th, 2007 at 12:34 amWhile you’re at it please fix the installer. I’ve tried multiple times to install Delphi 2007 trial but IT JUST DOESN’T WORK.
Install over the internet is a horrible idea. I want to download the full ISO and burn it to a CD.
Microsoft figured this out a long time ago. I don’t understand why CodeGear is unable to learn from other mistakes, instead preferring to make the same mistakes for themselves.
July 17th, 2007 at 12:38 amThis is a good decision. Afaik, CF is not important anymore. Major phone providers like Nokia, Motorola and Samsung have started to ship phones based on Linux. We can expect rise of Linux in mobile market in next year.
July 17th, 2007 at 12:40 amDid someone say Linux? …. could this latest move bring a reprieve for Kylix in the future?
July 17th, 2007 at 1:14 amNick,
I absolutely agree that CodeGear should refocus on the VCL and native designers, but I am intrigued to know - why *remove* functionality that is there? I would understand not upgrading it, but removing it seems odd - are there complications that would arise from keeping it?
And regarding the comment about Delphi developers instead of C# developers - I can’t speak for the Delphi user base in general, but I regularly develop in both C# and C++. I really do prefer Delphi, but it simply is not an island. Delphi apps need to interact with apps written in other languages and sometimes these different systems are housed in the same development team. This is why removing the functionality seems so strange - my team are now going to *need* to invest in VS.NET licenses that we would not have needed before.
July 17th, 2007 at 1:36 amGary- when do you think cg will learn that ther is money to be made with Linux to resurrect kylix ?
July 17th, 2007 at 1:39 amLinux? I don’t think so. We have Windows! It is so perfect. I now have a real nice shadow behind my windows in Vista. That shadow cost me € 450,00 but it is a very very good looking shadow. I know Mac and Linux has shadowed windows too. But i think the Vista shadow is much smoother.
July 17th, 2007 at 1:52 amPlease, continue the CF support, also without WinForms, but targeting both .net 1.1 and 2.0… I like Delphi.NET language as much as I hate C#…
July 17th, 2007 at 1:55 amThank you Nick, Codegear is taking the right way now. We are Delphi developmers, that is VCL for Win32 developmers
July 17th, 2007 at 2:05 amThis maybe a good decision. Maybe one of the better decision Borland/Codegear made. But it is just again another step in the "turn left, turn right" policy. How long will Delphi for PHP stay? Although I use php a lot I haven’t even looked at Delphi for PHP. Too afraid Codegear is going to drop it after version 3. Codegear needs A long-term _vision_ of there own. Just like when they made Delphi 1.0
July 17th, 2007 at 2:10 amNick, what brought you all those customers in the beginning? "I could do what I wanted in half the time than with any other tool" The tool I used was stable, fast to load, easy to use and a very reasonable price, allowing me to enjoy excellent return on my investment. I constantly "AWED" my customers with the next best thing that this tool had to offer.
Now, in my business I always use the approach: get back to basics, simply because my customers prefer basic business principles that work. They could not care less what the newest technology hype is or what the software giants are trying to sell them - I ALWAYS DOWN SELL them rather than up-sell them to the newest technology where applicable.
I am glad to see that CG finally realized that the GEM you have needs polishing, not more angles to make it shine. This is a good decision and I am a little more excited about Delphi’s future
July 17th, 2007 at 3:20 amWinForms is useless to me for my Delphi for .Net projects, and if duplicating/working around Microsoft’s Visual Studio only dependencies in C#/WinForms 2.0 takes away from new Delphi/VCL work, then I will gladly use another solution for my C# only projects.
I intend to be impressed. Don’t let me down.
July 17th, 2007 at 4:28 amHi Nick,
even though I think it’s sad that Delphi will lose some features I must applaud you: You made a tough decision and I think you made the right decision. If something must go, Winforms (which Microsoft wants to drop anyway) an C# builder are those parts of Delphi not many will miss.
On the other hand I too had to make a decision: Stay with Delphi for Win32 rather than try to migrate anything to Dephi for dotNET and Winforms. Looks as if this was the right one too.
twm
July 17th, 2007 at 5:16 amNick,
Look at what VS2008 will offer i.t.o. the shell that one can use to build your applications as plugins and redistribute. M$ are still being very clever here - get the end users used to a look and feel and inevitable force that look and feel design onto the developer’s custom apps.
Give us:
Firebird Support (Please Please Please),
A descent DB Designer in BDS for VCL,
Better looking VCL controls (Look at what Devex and TMS have to offer),
A competing grid to Devex, since they will no longer develop new products for VCL.
Mono integration and dependancy rather than .Net (This will make your (hopefully) planned support for linux a bit easier.)
Give us the leaps and bound we had from D2005 to D2006 in terms of quality!
B.T.W. Here in RSA, the major development is still being done in Java, so the battle hasn’t been lost.
Get out of the M$ box and give us loyal supporters yor best!
July 17th, 2007 at 7:11 amI have been a windows user since it came about. Windows Vista and the success of Apple has me wishing that I (and my company) could develop for Apple using Delphi. As an ISV, there is no money in Linux development on the client - Linux users want free software. There is also no reason to develop .net applications for a client machine (there is nothing you can do in .net that you can’t do native). Mac owners will shell out 700 bucks for a phone and a lot more for software. How difficult would it be to make Delphi compile to Leapord? Compiling to Leapord and Windows from one code base is THE killer application. I would buy codegear stock if they had a plan for doing this - it is the best (and possibly only) way to attract many, many new customers.
July 17th, 2007 at 7:57 amCharlie makes a great point. Developing apps for MacOS and Windows on a single code base would be the greatest feature CodeGear could provide to its developers. Apples’ OS market share is gaining plus this wouldn’t interest MS since they would want to keep developers solely in the Windows platform.
Forget about PHP, JBuilder, RoR. Concentrate your effort and resources in providing this feature for Delphi and CodeGear would be 10 times more successful. If Free Pascal can do it, why not CodeGear?
IDL
July 17th, 2007 at 8:33 amLachlan –
ASP.NET support is Delphi only. As I said — we are supporting Delphi developers.
Nick
July 17th, 2007 at 9:28 amLike many others, I think the decesion is very good. Microsoft is going to dominate winforms and asp.net. Moving into areas that Microsoft is ingnoring is a good niche to have. A major update to Delphi for PHP is needed soon to show the community that this is a product Code Gear is going to stand behind. I am looking forward to the strong future of Delphi.
July 17th, 2007 at 9:38 amNothing to criticize for me this time. Good move.
July 17th, 2007 at 10:10 amimplementing interoperation between .NET and Delphi Win32 (and later win64) sounds a win-win situation to me.
codegear will deliver the best product on the native development and at the same time allowing the delphi user to import code written in .net (most likely coded in c#).
July 17th, 2007 at 10:18 amNick,
I’m very glad about CodeGear’s decision not only because WinForms designer will be excluded from IDE, but because Delphi really is VCL. Recently I read something interesting. VCL is powerful, there is no doubt, but third components like DevExpress and Component One are excellent helpers in development. These component factories, few years ago, only works for MS/VS in .NET plataform. We have Nevrona and Atozed with us, but what we can do about that? Is there any plans with they in order to return to develop for Delphi/CodeGear?
July 17th, 2007 at 11:49 amNick,
What about Borland Data Provider and DBWebControls for ASP .NET?
July 17th, 2007 at 1:06 pmBDP and dbWeb components are going to be in the box, but they are deprecated.
Nick
July 17th, 2007 at 2:21 pm@Erwin van den Bosch
Just look at the possibilities came with the AIGLX and Beryl. You will have something worths mote than $495. Believe me.
July 17th, 2007 at 3:07 pmCharlie makes an interesting point. While there is no money in Linux, apple is a TOTALLY different ball of wax - there is a group willing to pay top dollar for even low quality apps.
Since Apple is based on BSD, a close design cousin of linux, it would be interesting to see if the kylix efforts could be rejuvinated for Apple’s OS. There I could actually see a small market willing to pay for it. Heck, I would probably be willing to upgrade my old G4 to the newest version of the MacOS if it had a reasonably priced version of Delphi on it. The only question is whether enough people would pay for it to justify it.
July 17th, 2007 at 5:44 pmCan WinForms controls (third-party, UserControls, etc.) be used in Delphi in VCL.NET projects? Can VCL.NET controls (third-party, TFrames, etc.) be used in Visual Studio in WinForms projects?
If the answer to both of those questions is "yes", then losing Delphi’s WinForms designer won’t matter much at all, because the interop opportunities will still be there. But if the answer to either is "no", then VCL.NET would be very unattractive to us as we move to .NET.
July 17th, 2007 at 9:29 pmI’ve just moved to an Apple MacBook because it is a better Windows box than my old Dell plus I get to see what the whole fuss is about with Mac OS X. I gotta tell you I am a convert and I would love to see a Delphi for Mac anytime soon. I am with Charlie on this one.
July 18th, 2007 at 3:54 amJoe,
This is exactly the point that i wanted to come. I Love VCL but there is no compatibility with them. third-party factories deploy only for MS/VS. My question is. What can whe do (CG in this case) in order to revert this situation? If we convert or design our applications on MS plataform, we will not enjoy this resource of third-party components.
July 18th, 2007 at 4:38 am1. Delphi is VCL. I agree. But VCL require some redesign. First is databinding. An existence of both TEdit and TDBEdit is a bad indicator.
2. ECO should be back-ported to Win32.
3. What are the reasons for VCL.NET. How is it better than VCL.Win32?
4. If .NET is almost not supported then may be it’s time to support other native-code platfoms like Linux? As a first step I would think about a deployment wizard to Wine (with registration of midas.dll etc).
July 18th, 2007 at 5:20 amJoe -> If you are moving to dotNet and don’t want VCL.Net, you might be better off checking out Chrome instead.
Maxim -> VCL.Net and vcl.win32 are not interchangable. One is a set of libraries of the dotNet platform, one is for the win32 platform. Oh, and they tried Linux, and it failed due to a number of unavoidable facts about linux.
July 18th, 2007 at 11:14 amFor everyone’s information. Markus Venter wrote that DevExpress was no longer writing for the VCL. THAT IS NOT TRUE! I asked their tech support and got a response from them stating that they never made any such announcment, and that they WILL continue to develop their VCL products. They even offered to let me talk directly to the company president on this issue. People should be very careful about spreading unfounded information. If you have evidence indicating that DevExpress is not continuing VCL support, post it so we can all see it.
July 18th, 2007 at 9:06 pmWhat planet are you people living on where there are no third party components for Delphi? Borland created the third party component market. It was not even a possibility for MS tools until Visual Studio. MS is still going around the globe trying to convince their users about the benefits of using commercial components. I have been using such controls all the way back to turbo Pascal 1.0! The Developers Express components existed for delphi years before they were available for MS. My company spends more than $10K (US) per year in subscriptions to thrid party controls. Those of you complaining about the lack of such components have been mis-informed, or have done very little research. I have never failed to find commercial Delphi components for any project requirements. All of this complaining about Delphi and Code Gear is ridiculous! Perhaps you people should just use a different tool. Whay are you here if you are so unhappy?
July 18th, 2007 at 9:13 pmDaniel,
I get the general feeling from all the posts here that most of us are very excited about the decision from Codegear.
http://community.devexpress.com/blogs/ctodx/archive/2007/06/19/fahrenheit-vcl.aspx
refers to Devexpress’s disconituation of it’s .Net controls for VCL. Where does that leave us who want to do .Net VCL development using ECO IV? We are also spending $$ per year on 3rd party components.
Not all of us are negative and not all of us are complaining. Our needs are just different from yours, but we love the same tool.
July 18th, 2007 at 11:39 pmI heard many people complaining about the lack of "databinding" in the VCL.
July 19th, 2007 at 2:24 amAFAIK it was a design choice to avoid to make standard controls dependent on DB units code, hence no DB code was linked in the executable keeping it smaller, and no DB package was required.
That’s not an issue with .NET where the whole framework gets installed to run an application.
Maybe nowadays executable size and package deployment are no longer a big issue, and I agree that some areas may need to be updated - but what .NET made may be not the right choice for the VCL too.
Daniel,
Markus Venter says that: if CodeGear discontinuate Windows Forms suport, they will not create components for DELPHI .NET. VCL components goes any way. I will find his de claration. So, DevExpress only Win32 for Delphi.
July 19th, 2007 at 7:26 amDigital Metaphros abandon their project for VCL .NET. They said. ‘Too much complicated…’
I always be very carefully with all my declarations.
But the question is. We have only Nevrona and Atozed. And the others? What we can do in order to get stonger our the VCL .NET?
For all. Here is the link.
July 19th, 2007 at 7:30 amhttp://community.devexpress.com/blogs/ctodx/archive/2007/06/19/fahrenheit-vcl.aspx
here is the link.
http://community.devexpress.com/blogs/ctodx/archive/2007/06/19/fahrenheit-vcl.aspx
posted form Markus Venter.
July 19th, 2007 at 7:35 am"First of all, a huge sigh of relief: no more WinForms in Borland Developer Studio (or whatever name it will now have). We can and will now firmly and rightly say: no, our .NET controls just won’t work in BDS. Sure, you can still manually type code to create them and set their properties and assign event handlers, but our controls never will never work in BDS at design-time. If you want to use our .NET WinForms controls and have a rich, interactive design experience, you should be using Visual Studio 2005 or later."
From Julian M Bucknall
July 19th, 2007 at 7:40 amMaybe it is about time CodeGear takes notice of the MacOS:
http://blogs.business2.com/apple/2007/07/apple-mac-sales.html
July 19th, 2007 at 9:20 amgood decision but toooooo late…
July 24th, 2007 at 5:27 amFabulous! Let that traitor Anders each all his Microsoft dog food himself. Lets get back to what Turbo Pascal, Pascal w/Objects and Delphi great.
OWL kicked MAJOR ass, VCL is damn good but it needs a little work and some updates to its wrapping but it still kicks but, it runs fast and it runs reliably,
Like others have eluded to, Delphi needs to go X-Platform in a major way and it needs to become THE killer development environment no matter what platform your on, be it:
Win32
OS-X ( AQUA )
Linux ( KDE & GNome ) *
Do these things the world will beat a pathway to the Delphi Door. Kylix was a damn good start and I use it today! The IDE is a little flaky but I save OFTEN and if it blows up I can get back to where is was by Force-Quit and restart.
Personally I think it should just be Delphi and it comes on a DVD and installs on any of the platforms named. You buy Delphi and you have your compiler and IDE for any platform you code for.
I use Delphi 5 Enterprise and find that its fast and reliable. I use the BDE and Native Oracle access DLL’s and it just screams against Oarcle 10g.
I am putting the finishing touches on a Point of Sale system that talks to Oracle and the only thing I could really ask for at this point is to be able to x-compile it to whatever platform my customer wants it on. It is written in pure VCL and it will compile under Kylix although I had to write a set of wrappers to handle the differences in the Database Components.
You give me that and its worth the $1300.00 upgrade price for Enterprise since a TEdit is a TEdit no matter whats its wrapped around, Win32, Aqua, Gnome, KDE
* To those that think people who run Linux as a Desktop environment don’t want to pay for software, well then your just not writing the right software. Good software where people can pick up a phone and get a support person on the line, to solve the problem that is effecting their business NOW are more then willing to pay for their software.
July 28th, 2007 at 10:22 pmOh yeah.. Stop using IIS, it sux.
July 28th, 2007 at 10:23 pmVery nice information. Thanks
July 29th, 2007 at 1:54 pmI wish CodeGear the best of luck with this.
As for the roadmap, would be great to get a roadmap which included MacOSX support. If it was possible to write a single app portable cross MacOSX, Windows and Linux it would be fantastic. If this same framework were to be usable from C++ and Delphi, so much the better.
August 1st, 2007 at 10:38 amJust some quick question:
- Generics?
- LINQ for Delphi?
- ASP.NET AJAX/Futures?
- EDM/Yukon support?
- Forget WinForms! What about Windows Presentation Foundation?
- Windows Workflow and Communication Foundation?
?????? and so on.
It’s near 2008 guys, .NET 3.5 framework beta 2 already has it.
August 8th, 2007 at 3:22 pmJust some quick question:
- Generics?
- LINQ for Delphi?
- ASP.NET AJAX/Futures?
- EDM/Yukon support?
- Forget WinForms! What about Windows Presentation Foundation?
- Windows Workflow and Communication Foundation?
?????? and so on.
It’s near 2008 guys, .NET 3.5 framework beta 2 already has it.
August 8th, 2007 at 3:23 pmJust some quick question:
- Generics?
- LINQ for Delphi?
- ASP.NET AJAX/Futures?
- EDM/Yukon support?
- Forget WinForms! What about Windows Presentation Foundation?
- Windows Workflow and Communication Foundation?
?????? and so on.
It’s near 2008 guys, .NET 3.5 framework beta 2 already has it.
August 8th, 2007 at 3:27 pmsupport linux,support aix,support hp unix
August 16th, 2007 at 7:58 pmReduced to the max! Everybody doing serious work has been sitting on the fence anyway getting work done in Delphi 7 and waiting for the fog around .NET to clear.
Migration to .NET starts to make sense as soon as we can recompile the VCL programs as RIA into Silverlight. Then we’re finally on the web without rewriting the whole thing.
September 5th, 2007 at 12:19 amNice site. Thank you!!!
October 31st, 2007 at 6:10 pmI’ve been working with Delphi since version 1 and it is my system of choice. Unfortunately, I have an important client who wants my Delphi programs moved to C# and I am finding the experience a waste of time and way beyond painful. C# is OK (Anders’ touch?) but I still prefer Pascal. Visual Studio is unstable and unfriendly and NET (ADO.NET in particular) makes the VCL look like the jewel it is. I find it takes FAR more effort to get NET programs to do things which Delphi did easily, when they can do them at all. In short, Delphi is far more productive. I just wish it was successful enough to convince IT departments to accept it. Good luck, I hope I get a chance to use your new products soon.
November 18th, 2007 at 2:46 pm