vb6 to dot.net migration

[Irfan S. Fazli]

I need your guidance to enlighten me on the path to follow on migrating our
(very large) application written in vb6 to vb.net (2005 ed).
Microsoft tech-professionals have assured us that this can be done in a
trice. No problem. I strongly doubt them.
Some links or ideas will be greatly appreciated.
Thanks in advance.
--
IRFAN.

[Greg Young]

Well it is fairly applicationd ependent .. you might quickly use the
migration tool to migrate the code but I can assure you that you will end up
with a complete rewrite in the long term.

The fact that VB.NET is not truely OO will pretty much force this to happen.

Cheers,

Greg
"Irfan S. Fazli" <Ir*********@discussions.microsoft.comwrote in message
news:AF**********************************@microsof t.com...

>I need your guidance to enlighten me on the path to follow on migrating our
(very large) application written in vb6 to vb.net (2005 ed).
Microsoft tech-professionals have assured us that this can be done in a
trice. No problem. I strongly doubt them.
Some links or ideas will be greatly appreciated.
Thanks in advance.
--
IRFAN.

[guy]

Greg, I hope you meant 'VB 6 is not truely OO' - dont frighten the OP too
much! But you are correct, migrating a large VB6 app is a lot of work - and a
lot of planning

guy

"Greg Young" wrote:

Well it is fairly applicationd ependent .. you might quickly use the
migration tool to migrate the code but I can assure you that you will end up
with a complete rewrite in the long term.

The fact that VB.NET is not truely OO will pretty much force this to happen.

Cheers,

Greg
"Irfan S. Fazli" <Ir*********@discussions.microsoft.comwrote in message
news:AF**********************************@microsof t.com...

I need your guidance to enlighten me on the path to follow on migrating our
(very large) application written in vb6 to vb.net (2005 ed).
Microsoft tech-professionals have assured us that this can be done in a
trice. No problem. I strongly doubt them.
Some links or ideas will be greatly appreciated.
Thanks in advance.
--
IRFAN.

[Cor Ligthert [MVP]]

Greg,

Or that you do mean in addition to Guy that VB.Net is truely OOP. VB6 is as
well OO.

Although I have seen lately a complete non OO writen C# program do I agree
with you that a good team will sooner or later go to OOP.

Cor

"Greg Young" <dr*******************@hotmail.comschreef in bericht
news:uw**************@TK2MSFTNGP04.phx.gbl...

Well it is fairly applicationd ependent .. you might quickly use the
migration tool to migrate the code but I can assure you that you will end
up with a complete rewrite in the long term.

The fact that VB.NET is not truely OO will pretty much force this to
happen.

Cheers,

Greg
"Irfan S. Fazli" <Ir*********@discussions.microsoft.comwrote in message
news:AF**********************************@microsof t.com...

>>I need your guidance to enlighten me on the path to follow on migrating
our
(very large) application written in vb6 to vb.net (2005 ed).
Microsoft tech-professionals have assured us that this can be done in a
trice. No problem. I strongly doubt them.
Some links or ideas will be greatly appreciated.
Thanks in advance.
--
IRFAN.

[Greg Young]

whoops it was late .. you know what I meant though :)
"guy" <gu*@discussions.microsoft.comwrote in message
news:C9**********************************@microsof t.com...

Greg, I hope you meant 'VB 6 is not truely OO' - dont frighten the OP too
much! But you are correct, migrating a large VB6 app is a lot of work -
and a
lot of planning

guy

"Greg Young" wrote:

>Well it is fairly applicationd ependent .. you might quickly use the
migration tool to migrate the code but I can assure you that you will end
up
with a complete rewrite in the long term.

The fact that VB.NET is not truely OO will pretty much force this to
happen.

Cheers,

Greg
"Irfan S. Fazli" <Ir*********@discussions.microsoft.comwrote in message
news:AF**********************************@microso ft.com...

>I need your guidance to enlighten me on the path to follow on migrating
our
(very large) application written in vb6 to vb.net (2005 ed).
Microsoft tech-professionals have assured us that this can be done in a
trice. No problem. I strongly doubt them.
Some links or ideas will be greatly appreciated.
Thanks in advance.
--
IRFAN.

[Greg Young]

I have also seen alot of C++ that looks like C :)
"Cor Ligthert [MVP]" <no************@planet.nlwrote in message
news:uG**************@TK2MSFTNGP04.phx.gbl...

Greg,

Or that you do mean in addition to Guy that VB.Net is truely OOP. VB6 is
as well OO.

Although I have seen lately a complete non OO writen C# program do I agree
with you that a good team will sooner or later go to OOP.

Cor

"Greg Young" <dr*******************@hotmail.comschreef in bericht
news:uw**************@TK2MSFTNGP04.phx.gbl...

>Well it is fairly applicationd ependent .. you might quickly use the
migration tool to migrate the code but I can assure you that you will end
up with a complete rewrite in the long term.

The fact that VB.NET is not truely OO will pretty much force this to
happen.

Cheers,

Greg
"Irfan S. Fazli" <Ir*********@discussions.microsoft.comwrote in message
news:AF**********************************@microso ft.com...

>>>I need your guidance to enlighten me on the path to follow on migrating
our
(very large) application written in vb6 to vb.net (2005 ed).
Microsoft tech-professionals have assured us that this can be done in a
trice. No problem. I strongly doubt them.
Some links or ideas will be greatly appreciated.
Thanks in advance.
--
IRFAN.