I have a pretty big VB6 project. Every day I'm getting requests from my boss
to add some new features or change existing ones. So I do not see any easy
way to rewrite an existing project using VB.Net, just because I will have to
work with 2 versions simultaneously - for instance I rewrote let's say 5
modules and they work in .Net. A new request requires to change something in
one of the modules which exist in both versions, so I will need to make
changes in both.
I made some research and found out that I can use in VB6 DLLs created in
..Net.
If so, I think that I could replace some modules in an existing VB6 project
with the same functionality objects written in VB.Net.
For instance I have many forms in VB6 which are used to do several kinds of
searches. I can replace one of them with .NET DLL, containing Class and
Form doing the same search.
In this case I would replace module by module until the final step, when
I'll create a new .NET project and bring all the DLLs written before into
that new project.
This approach will allow me to move from VB6 to .NET step by step without
the need to work with 2 projects at the same time.
Tell me where my logic is wrong and maybe there is a better solution for an
upgrade?
Thank you
Al
to add some new features or change existing ones. So I do not see any easy
way to rewrite an existing project using VB.Net, just because I will have to
work with 2 versions simultaneously - for instance I rewrote let's say 5
modules and they work in .Net. A new request requires to change something in
one of the modules which exist in both versions, so I will need to make
changes in both.
I made some research and found out that I can use in VB6 DLLs created in
..Net.
If so, I think that I could replace some modules in an existing VB6 project
with the same functionality objects written in VB.Net.
For instance I have many forms in VB6 which are used to do several kinds of
searches. I can replace one of them with .NET DLL, containing Class and
Form doing the same search.
In this case I would replace module by module until the final step, when
I'll create a new .NET project and bring all the DLLs written before into
that new project.
This approach will allow me to move from VB6 to .NET step by step without
the need to work with 2 projects at the same time.
Tell me where my logic is wrong and maybe there is a better solution for an
upgrade?
Thank you
Al
Comment