-
Jan 12th, 2018, 05:58 AM
#1
Thread Starter
Frenzied Member
Running VB6 now starts up Windows installer
I traced it back to a broken addin, the Package and Deployment Wizard. For some reason, as long as PDW is enabled, whenever VB6 starts up it starts running the Windows installer. It didn't give me a problem before though. The key as to what is causing the problem is what the Windows installer claims to be trying to install. It claims to be trying to install Visual C++ 2005. Recently I actually did install Visual C++ 2005, so I would be able to do some programming in C++ as well. Somehow, a file or registry entry for VB6's PDW must have been corrupted when I installed Visual C++ 2005, and corrupted in such a manner as to trigger Windows installer to try to install the last thing that was installed.
I've fixed the problem temporarily, by disabling the PDW in VB6 for now, but I don't want to keep it disabled, as it is the only way for VB6 to generate an installer, and that is needed for any program that I want to make sure the end user is able to conveniently install (without having to manually copy the program's files, and manually register OCX and ActiveX DLL files). The average computer user doesn't even know about regsvr32, or what the phrase "register an activex dll" even means. So without an installer, most end users would have no way to even get most programs working, as most programs depend on at least some basic OCX files (for example, Common Dialog or Winsock).
Is the problem I'm encountering with PDW, or other addins in VB6, triggering the Windows installer a common problem? If so, please tell me how to fix it. Is there some file or registry entry I could manually repair?
Last edited by Ben321; Jan 12th, 2018 at 06:01 AM.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|