"Gillard" <gillard_georges@@@@@@@@@hotmail.comwrote in message
news:uO**************@TK2MSFTNGP04.phx.gbl...
vb6 can only target 32bit platform
"rcook349" <rc***@westinis.comwrote in message
news:53**********************************@microsof t.com...
>I have a friend who's small company is on VB6 and SQL2000 for their apps.
They would like to know what arguments (high level) there are for
upgrading to the current version/platform of VB.NET 2008 and SQL2008.
Saying "newer/better/faster" isn't a strong enough argument when the
counter to that could be "if it ain't broke, don't fix it".
Coming from the other side of the tracks here... but, really... If it ain't
broke *don't* fix it.
If you're not writing new apps, there's no reason *at all* to migrate...
note that I say "migrate" and not "upgrade". Considering the dog/slow IDE
and the "everything including the kitchen sink - except VB specific
debugging utilities" approach to the environment... and the fact very little
code you have now will migrate without inspecting each line carefully, I
certainly wouldn't attempt to try and migrate any projects to a "less
friendly for VB" environment. (dotNet fans, save your typing, I'm not
talking about the LINQ, etc bandaids that *clearly* aren't based on the VB
language - I don't do database apps. Period)
"newer/better/faster" would only apply to "all new" development... and, even
then, if you're talking about desktop apps and haven't hit any limitations,
why bother.... besides, the jury's still out on the "better/faster" part...
no one's convinced me that dotNet's faster at *anything* and it's been out
for what.... 8 years now?.. and "better" is purely a matter of opinion...
personally, I don't like the environment. Since I've mentioned my gripes
many, many times, I won't bother now.
--
Ken Halter
Part time groupie