For many of the reasons others have mentioned, I chose to make the leap from
vb6 to c# some time ago. Conversion of a vb6 app to .net can be a tedious
exercise. I chose to just rewrite it in c# and take that opportunity to
learn a new language and clean up some of my previous "features".
 If you look around the internet, you'll see all sorts of languages that run
in .Net (Cobol, Perl, Forth, etc). Pick the one(s) that work for you. I'm
kinda surprised that no one has jumped and written Pick
Basic.Net<http://Basic.Net>yet... :-)
 On 4/28/05, Key Ally <[EMAIL PROTECTED]> wrote:
>
> John,
> Or look at Delphi, which supports .net from release 7 and forward.
> VB.net <http://VB.net> has much more in common with Delphi than with VB6.
> And moving
> from VB6 to Delphi is less culture shock than VB6 to VB.net<http://VB.net>
> .
>
> - Chuck
>
> David Jordan wrote:
>
> >If you are looking to move from VB6 because Microsoft is dropping support
> in
> >the next few months, the other option is to look at business basic. This
> is
> >similar to VB6, has a conversion utility and can run on Linux.
> >
> >-----Original Message-----
> >[mailto:[EMAIL PROTECTED] On Behalf Of John Kent
> >Is there any advantage of using C# to VB seeing that microsoft seem to be
> >committed to supporting both.
> >I should imagine its going to be easier to convert legacy vb to
vb.net<http://vb.net>
> >rather than vb to c#
> -------
> u2-users mailing list
> u2-users@listserver.u2ug.org
> To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to