On 1/4/2019 6:35 PM, Mayayana wrote:
"Mike" wrote

| Microsoft will do whatever they can to encourage you to
| move to win10. One subtle move is to change the software
| development environment in such a way that it forces vendors
| to maintain two separate versions of their product.

?? I don't know what you're referring to. I work
in VB6 and can write software that runs on virtually
any existing Windows computer without installing
any support files. Are you talking about Metro?
Or something else?


I can't give you any examples.
I've been retired and out of the business for 24 years.
If MS makes subtle changes in the API that causes you to need different
syntax, that's all it takes to require two separate code bases to be
required/maintained. Historically, one such change was the change from
VB6 to dotnet.

You are stuck in the past, as am I, with VB6. You can build whatever
VB6 and the support API allows. My guess is that major commercial
vendors find that newer IDE/languages are much more productive in getting
all those bugs to the user as quickly as possible. Once you've done that,
you can leverage other existing modern code, but
supporting older versions with different coding constraints becomes
expensive.

Having said that, maybe you can help me extend the life VB6.
My needs are simple. VB6 can do everything I've needed so far.

I have VB6 working in windows 10.
I can write and execute code on the machine that has VB6 installed.

What isn't working is the package deployment wizard that lets me install
the program on another computer without resident VB6.
Got any advice on fixing that?

Best thing I have so far is to move the finished
code over to a win7 virtualbox and execute the deployment wizard there.
I don't just code/debug there because most of my stuff is hardware interface
and VBox gets in the way.

Email works if that's off topic.

Thanks,
mike