XP VB6 program to run on new Windows OS

I have a number of programs written in VB6 under XP that I now need to install on modern Windows OS’s. There is a back-compatibility issue.

The major problem is MSFLXGRD.OCX

I use “inno” to build the installer exe. Here is the significant line from the inno script. A critique would be appreciated:

Source: "C:\ <path goes here> \MSFLXGRD.OCX"; DestDir: "{sys}"; Flags: restartreplace sharedfile regserver

I’ve successfully done this with one of my programs. It installs and runs on Vista, but runs slowly. I suppose that is to expected.

I need some advice for the future:

Should I bite the bullet and get myself up to date? Which new OS?

Should I migrate my programs to VB.net? That will be a chore, but does this have anything to do with OS compatibility? Is such a move worth the trouble?

- - Norma
NormaPosyPhysicistAsked:
Who is Participating?
 
Guy Hengel [angelIII / a3]Connect With a Mentor Billing EngineerCommented:
if you need to keep VB6, to deploy the .ocx, use this tool:
http://www.dependencywalker.com/
it will help you to know which other .dll have to be included in the package.
0
 
Éric MoreauConnect With a Mentor Senior .Net ConsultantCommented:
>>Should I migrate my programs to VB.net?

You need to be aware that it is a complete rewrite, not just opening the old project in the new IDE and you're done.
0
 
NormaPosyPhysicistAuthor Commented:
Thank you.

The line of inno script in my posting puts the OCX in sys rather than installation target folder, and carries necessary directives. Otherwise, the newer OSs don't know what to do with it.

Yes, I'm aware that going to VB.net is not a simple thing. But at least all my hard work getting the program flowcharts right is still valid.
0
All Courses

From novice to tech pro — start learning today.