Delphi to C# Migration

Question

Hi All I wonder if someone could proffer advice on the benefits  the cost  and most importantly the risks of migrating Delphi applications/codes to C#. The big guns of the company is very much inclined to go ahead with this migration. Thank you in advance.

Ankur Jain · Answer

Hi! please take a look at following links....if these solve your problem please don't forget to marked it as answer.... http://www.codeproject.com/Articles/310667/NET-Code-Conversion Delphi has some considerable advantages for Win32. Not that .NET apps are inherently bad but try: running a .NET app (any version) on Win95/ME where .NET doesn't exist (AFAIK) distributing any small ( providing any .NET app on a system that has no Internet access (yes they exist) distributing your .NET apps in countries without widespread high bandwidth keep people from seeing your source code without spending a ton of dough (Reflection anyone?) Garbage collection in .NET might be really nice but anyone who knows anything about programming can also handle manual allocation/deallocation of memory easily with Delphi and GC is available with reference-counted interfaces. Isn't one of the things that brought all of the non-programmers to proliferation the pseudo-GC of VB? IMO GC is one of the things that makes .NET dangerous in the same way VB was dangerous - it makes things too easy and allows people who really have no clue what they're doing to write software that ends up making a mess. (And before I get flamed to death here it's great for the people who do know what they're doing as well and so was VB; I'm just not so sure that the advantage to the skilled outweights the hazards to us from the unskilled. ) Delphi Prism (AKA Rem Objects Oxygene formerly Chrome) provides the GC version of Delphi that those who need it are looking for along with ASP.NET and WPF/Silverlight/CE with the readability (and lack of curly braces) of Delphi. For those (like me) for which Unicode support isn't a major factor Delphi 2007 provides ASP.NET and VCL.NET as well as native Win32 support. And at a place like where I work when workstations are only upgraded (at a minimum) every three years and where we just got rid of the last Win95 machine because it wasn't a priority to upgrade the .NET framework is an issue. (Especially with company proxy requirements only allowing Internet access to a handful of people limiting bandwidth and download capabilities and proper non-admin accounts with no USB devices allowed all still running across a Netware network - no such thing as Windows Update and never a virus so far because nothing gets in.)