Hi all,
I am working on a VB6 application ( .NET is forbidden for now) and wish to hear from people who have OO design experience in both .NET and VB6.
I would like to know which VB6 OO techniques should be used with a view to easing a .NET migration a few years later.
I am thinking of a scenario where a partial migration to .NET can be made possible with the use of COMInterOp.
The planned VB6 client-server application is reasonably complex but performance and scalability are not very high up on the list of requirements. I see therefore a mixed environment .NET/COM situation shaping up due to: [ul]
[li].NET components used to increase standardisation (common .NET routinees/services, e.g. ?XML);
[li]VB6 portions might remain due to use of APIs and functionalities (e.g. automation and use of 3rd party OCX) not easily replicated in .NET
[/ul]
I have followed some information on Microsoft sites on VB migration and upgrade, but did not find sufficient material on how to create a durable (from .NET perspective) OO design in VB6. Instead there are specific upgrade / compatibility notes that do not address the big picture.
Thanks in advance for help provided.
DavidQR
10 Nov 2003
I am working on a VB6 application ( .NET is forbidden for now) and wish to hear from people who have OO design experience in both .NET and VB6.
I would like to know which VB6 OO techniques should be used with a view to easing a .NET migration a few years later.
I am thinking of a scenario where a partial migration to .NET can be made possible with the use of COMInterOp.
The planned VB6 client-server application is reasonably complex but performance and scalability are not very high up on the list of requirements. I see therefore a mixed environment .NET/COM situation shaping up due to: [ul]
[li].NET components used to increase standardisation (common .NET routinees/services, e.g. ?XML);
[li]VB6 portions might remain due to use of APIs and functionalities (e.g. automation and use of 3rd party OCX) not easily replicated in .NET
[/ul]
I have followed some information on Microsoft sites on VB migration and upgrade, but did not find sufficient material on how to create a durable (from .NET perspective) OO design in VB6. Instead there are specific upgrade / compatibility notes that do not address the big picture.
Thanks in advance for help provided.
DavidQR
10 Nov 2003
