which is better visual basic 6 or visual basic.net
MS Visual Basic 6.0 is obsolete, having long ago been replaced by
MS Visual Basic.Net
Steve
That is a matter of opinion. Copies of VB6 are still being sold on ebay and
programs are still being written. Giving up VB6 and going to .Net is, in
the eyes of some, not progressive at all.
In the end, the answer depends on what you want to do. You can, after all,
still obtain very good windows versions of Fortran....and this works very
well for certain applications.
Re: What this mean for Borland? ... As a matter of fact Borland did the opposite mistake with Delphi for .NET imho - Delphi needed to change for .NET, and they failed to do so - but that's a topic for a different discussion). ... That said VB6 isn't going anywhere, so it's not like developers that have exiting applications written in VB6 cannot continue to use VB6 to maintain these apps, or even continue using VB6 to write new applications. ... (borland.public.delphi.non-technical)
Re: FAO Colin D :) ... The actual subject matter of the Website is quite pertinent ... to me at the moment as I have been lamenting maintaining legacy vb6... MP4858 "Be who you are and say what you feel, because those who mind... - Dr. Seuss... (uk.rec.bodybuilding)
Re: Playing with the Dark Side ... I still look at this way....I can write nearly the identical app with the identical features in 1/4 of the time with VB6 than it'd take me in VB2005. ... It's a matter of using the right tool (in this case a programming language) for the job that needs to be done. ... (microsoft.public.vb.general.discussion)
Re: logonuser api returns 127 ... Using GetLastError in a .NET or VB6 for that matter is ... You should use the LastDllError property or the ... (microsoft.public.dotnet.languages.vb)
Re: Array of Objects ... I don't recall being able to do this in VB6,... way you are showing it. ... it would be a simple matter of: ... (microsoft.public.dotnet.languages.vb)
