Tuesday, September 07, 2004

From borland news: "Help required - have you any advice or views for moving away from VB6"

John Schirn wrote:
> I'm looking to make a move away from developing in VB6 to either
> Delphi (7 or 8?) or C# - any experience that you have had that
> would help me judge the implications of the different options
> would be much appreciated.
> I currently develop in VB6 (6 yrs), with previous background in
> Clipper 5.2 (5 yrs) - systems developed range from 3-tier
> multi-user using an MS-SQL database to desktop stand-alone
> applications using an Access database. Have developed a number of
> standard components/routines that re-use between projects, and
> make use of features such as objects/implementation.
> The way ahead seems very unclear - currently considering the pros
> and cons of, but not necessarily restricted to, Delphi, Borland
> C# or Studio.Net (either VB.Net or C#). I have browsed various
> articles and discussion groups and it seems that when comparing
> Delphi (7) and VB6 there was a lot of support for the Delphi case
> (that did make me think maybe I should have gone Delphi instead
> of VB back in the mid 90's! - but I didn't and now have a lot
> code/experience in VB). I haven't yet though found a thorough
> review comparing Delphi 8 (.Net compatible) with VB.Net and/or
> C#.Net - although I expect a lot of VB developers are currently
> in the same position as me.
> It seems I'm going to come up against a learning curve either
> way, I want to be confident that after putting in the effort I
> will:
> a.. Learn a language/development environment that promotes well
> structured code and facilitates sensible re-use of code within
> and between projects b.. Produce applications quickly without
> re-inventing the wheel every 5 minutes
> c.. Produce applications that are robust and easy to use
> d.. Use a language/development environment that looks set to
> have strong on-gong support and be regarded as a primary choice
> well into the next generation of Windows.
> e.. Apps that are easy to install/upgrade on variety of spec/OS
> version machines (at least different versions of Windows!).
> OK a lot (if not most) of what creates the above qualities is
> independent of the language itself - but some languages can make
> it more likely than others!
> It seems that many of the advantages that Delphi had over VB6
> have been addressed to some extent with .Net (inherited forms for
> example) - what advantages does Delphi 8 have over VB.Net or
> C#.Net? Or should I be seeing a non-.Net Delphi 7 as a medium
> term option?
> Specifically what I would like to know is, does anyone with
> experience of both Delphi 5, 6 or 7 and Delphi 8, and some
> knowledge of what C# and/or VB.Net have to offer, have a view on
> the merits of either option?
> a.. Is Delphi 8 only for use with MS Windows .Net operating
> systems? b.. Is Delphi code portable between Delphi 7 and 8
> (either way)? c.. Has C#/VB.Net caught up with Delphi (e.g. in
> ease of use and design-time functionality of form inheritance?)
> d.. Can Delphi 8 code/applications be compiled for non-windows
> operating systems - Is there any similar option for C#/VB.Net?
> e.. Can third party .Net controls be used with non windows
> forms (VCL?) and for non-windows operating systems?
> f.. Is Delphi 7 case sensitive (for variable names etc.)? Is
> Delphi 8 case sensitive (for variable names etc.)
> g.. What is the learning curve for C# compared to Delphi for an
> ex-VB programmer?
> Am I missing any important factors to consider?
> I would be very grateful for any view on these questions.
> John S


jordan said...

I found a lot of useful info about sql database on your blog - thank you. I also have a new sql database tips blog - please click over and have a look

mia said...

I found a lot of useful info about sql database on your blog - thank you. I also have a new sql database tips blog - please click over and have a look