I am trying SB Developer to create an installer for my Visual Basic 6 product. I've looked in the Manual and haven't been able to determine the following; I can see how to add the VB6 runtimes but have a question; The VB6 runtimes appear to all get installed in the same direction as my application. That is undesirable. It looks like I can install them elsewhere; but if I do will there be any steps needed to 'register' them?

Installshield For Vb6 Tutorial Database. 1/27/2018 0 Comments. Hi I made an VB6 app, and a couple of DLLs written for that app. I want to use Visual Studio Installer to install the whole app (exe+dlls) but I'm having problems with the DLLs. I made an installer project using the VSI's Visual Basic template and it works ok on my PC, but on. This is a pretty basic tool for authoring Windows Installer packages, but it should meet your needs. Along with this you'll want the recent merge modules for your dependencies: Merge Modules for Service Pack 6 for Visual Basic 6.0 and Visual C++ 6.0.

Will my program be able to 'find' them? I have experience with Install Shield Express and that product by default seamlessly and invisibly installs the VB runtimes 'somewhere else' (windows/system???) and then registers them. Does SetupBuilder Developer provide something similar, or if not how do I manually do it? Please advise - thanks! Hi Friedrich, I built one installer and did a trial 'installation' with it and it successfuly installed the program and when I looked in the installation directory all I saw was my executable file. Then I went back to SB and did a 'Dynamic Scan' of my program and built a new installer and ran it.

COMPLETE • LIMB PENETRATION Implemented limb penetration (forearms no longer block headshot or torso damage). • ADS FIX Fixed the “ADS bug” that causes ADS to cancel when shooting on uneven ground / falling a tiny distance (or seemingly at random).

This time when I looked in the installation directory I still saw my executable, plus a lot of files that look like part of VB6; mscomct2.ocx commctl32.ocx tabctl32.ocx and others. Plus a larger number of files that I don't recognize; PENUSA.DLL dwmapi.dll tiptsf.dll and too many more to type.

I should mention the platform I did the test install on had previously had a VB6 program installed on it, so maybe it already had some stuff on the machine. In any event my baseline question is; - What do I need to do to make sure all support files needed to run my VB6 app are installed, if not already present on the target machine, and can it be done without inserting them into the same target directory as my executable is going into? Thanks a lot!!! Bob, Dynamic Scan monitors your system as you execute an application, automatically determining which 32-bit DLLs and OCXs (dependency files) are used by the application.

This is only to help you find out which dependency files are called. You (as the developer of the application) have to decide which files have to be redistributed. And you should never ever redistribute any 'system' file from your own system because there might be a difference between operating systems. For example, the penusa.dll component is the Microsoft USA Handwriting Input UI. You application (or a component used by your application) calls into this dll. So the question is, do you really have to redistribute that file and do you have the rights to distribute it. Only you, the developer, knows the answer.