When will VB6 be Unable to Run Under Windows

[gibra]

That statement could actually be misunderstood by people who accomplished and run
a working VB6-installation on Vista up to Win10, but didn't use your Installer to do so...

A clear statement from you, what those people would have to do in *addition*
(on their "normal" VB6-installation), to be able to safely run the IDE non-elevated
would be nice, to not mislead them into thinking that this switch is not necessary.

Olaf

The issue is complex because it involves many factors that are not always easily understood by a developer that does not mean these things.
Especially when 'transmitted' via web, they may be even less clear.

For a correct installation, also require to edit manuallly some files. It is not so easy to explain, and even less to make it clear. There is a study, behind all this.

There are many 'guides' in the web that indicate how.
More or less, these guides give correct information, but these indications were valid at that time.
For example, since its release Windows 10 TP, I already have done three updates to my wizard (the latest 4.3 version just yesterday).
Unfortunately MS likes to change the rules: from version to version, from build to build, so the problem is not 'how to' but became 'how do IF ...'

The IF is for:
- Windows version
- Version of VB: From Visual Studio 6.0 or from Visual Basic 6.0 distribution ?
- Edition of VB: Professional or Enterprise ?
The combinations are different, each with different problems!

Moreover, not all distributions of VS/VB seem to be exactly alike, can also be different from the localized language.
For example, on some distributions, the MSDN Library CD folders structure of Italian language is different of English language.

In addition, the Retail version of Visual Studio is different from the MSDN Subscription version:
IE4 folder doesn't exists in Subscription version, so MSJAVA.DLL doesn't need to be copied con C:\Windows (setup run correctly without it).

As you can see, the problems are many and different.

It 'easy to understand that explain all this in a comprehensive manner requires writing a guide long and complex, and here we return to the starting point: those with little or insufficient knowledge of these issues will eventually make just a mess and will be disappointed.

My VS6I Wizard tries to solve all these problems in an automatic and transparent to the user.


When I thought of designing my VS6 Installer wizard, I did it because I was tired (whenever I had to re-install Windows on my PC) than reading a guide (found on the web) to manually change the setup of my Visual Studio 6.0 Enterprise Edition (ITA), the only tool I had created for my personal use.
Next, seeing that many, like me, had increasingly complex problems in installing Visual Basic 6.0 so I decided to make the wizard public (and free), for others to solve the problems that I had to face.

Experts do not need my tools, they already know how to do.
It is the less experienced who find themselves in difficulty, I hope that my tool could be helpful, and, given the number of downloads (over 49.000), it seems to be appreciated.