"Stan Canepa" <sc*****@docksidesoftware.com> wrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl...
Thanks for the input. I thought it might help if I give a little more
details about what I am trying to do. I have very large VB 6 application
with several modules. And at some point we are going to have problems with
VB 6 apps not running are running proficiently on newer OS, and I will
have
to do a rewrite. I am expecting the rewrite to take roughly 2 years, and
don't want to wait until I am forced to do it because of the time required
to do it.
So, I was looking for input as to why Dot Net is better. Some time frames
of
when I might start having problems with the OS. Just opinions on when
people
feel we may have problems finding VB 6 developers. I am basically looking
to
put together case for the rewrite and a time frame as to when it should
take
place, so that I can take it to the board for approval.
Thanks again
Since I have no dotNet projects, I'll answer from "the other side of the
fence" <g>. By the time VB6 just won't run anymore, several versions of
dotNet will have been released. They're already "advertising" VB9 (hate the
name 'cuz it just ain't VB, it's B#)
Future Versions
http://msdn.microsoft.com/vbasic/Future/default.aspx
imo, the best thing you can do, right now, at this point in time, is open
that VB6 project and start commenting the heck out of it. VB6 is already
"pseudo code like" so find any parts of your app that aren't crystal clear
just by looking at the code and either A) comment the code heavily or B)
(preferred) re-write for clarity, using VB6.
Then again, since you mentioned "take it to the board for approval", I
assume that company is large enough to support "a board" <g> so, if money's
not an issue, you can start the re-write at any time.
fwiw, keep the URL to my website handy. As long as you have that, you won't
have any problems finding at least one VB6 developer <g> Regardless of the
language(s) I'm forced to use at work, VB5/6 is my all time my favorite and
I plan to continue development as long as there are PCs available that'll
run Win2k or XP.
Side note: Don't expect any performance increase on a desktop app when
migrating a VB6 app to dotNet. With all the overhead dotNet has, it would be
hard to compete with a fully compiled language such as VB6. Especially for
small "do it now and get it over with" type apps.
--
Ken Halter - MS-MVP-VB (visiting from VB6 world) -
http://www.vbsight.com
Please keep all discussions in the groups..