Quote Originally Posted by jmcilhinney View Post
But you didn't write a Delphi app in 1995. You wrote a VB6 app so surely it would be easier to migrate it to VB.NET, which shares a syntax and reimplements a lot of VB6 functions, than to move to a completely new language like Delphi.
you are right, and what a big mistake. Because if I chose the latter(vb 6), with only small mods at a time I would have my app compiled on the latest version today.

Emulators will not work for me, my customer expect the app to run just like any other, jumping through hoops is not acceptable.

So here is my train of thought.

Lets say I move from vb6 to .net. I would pretty much have to re-write my app for many reasons, the last import I did rendered 80,000 errors in vb.net.
So after all that work I would have the same app as I do now, but it may run slower, is not native and open to de-compilation. Yes I know .net native is coming but who knows how that will turn out. And at the end I am still at the mercy of MS who killed 100k lines of my code for the sake of OOP purity, and can only run on windows.

So lets say I re-write to delphi. BTW there is a convertor that would convert many of my classes which would speed things up. So what is the benefit: I get a native compiled app, that is able to be run cross-platform, maybe with better performance, on a language that has not broken previous versions completely like vb6- .net, that is open source, and free, with syntax that is more like vb6 than c++(QT Creator). I really think there is no competition here. As much as I hate moving to delphi because of some of the strange syntax, I think it is the right choice for me.