Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6012655
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T02:26:08+00:00 2026-05-23T02:26:08+00:00

I have a vb6 activex document project and I need to create an msi

  • 0

I have a vb6 activex document project and I need to create an msi package (thats what is the requirement since it has to be deployed thru active directory) that runs without any user interface and user intervention. I followed these steps:

  1. I created an msi project using visual studio installer and removed all the user interfaces. Added all the vbd files manually to the project, compiled it. When I run the msi, it intalls all the files without prompts but the application doesn’t run.

  2. I created a package using package and deployment wizard, then opened the source code of vb pdw project, commented all the message boxes, assigned default values where required. Then compiled setup.exe file and copied/overwrote it with the setup.exe on the install package created earlier. When I run it from command prompt like this ‘setup.exe -s install.log’ it installed the application without prompts, works well. And the application runs well after installation.

  3. So I decided to create an msi package using visual studio 2008 and added the above created install package (using package and deployment wizard). In custom action I set the setup.exe to run with ‘-s install.log’ arguments. I need one registry entry that holds the App path, so I added it on the registry settings section.

Another requirement is I need to run another self-extracting exe after the installation. And that self-extractor will look at the above registry entry and extracts (overwrites) the file on the App path.

So using custom action, I set the update.exe to run after the installation.

Now, when I run the msi, it runs well, and after installation it runs the update.exe, everything works well; but only sometimes. I couldn’t predict when it works and when it doesn’t. When I tried the same msi on few other machines, it worked on some and not on others.
And when I checked the ‘Add or Remove programs’ there were many entries for this App.

I have been struggling with this msi project for a while and now I feel helpless. I don’t know what I’m doing wrong. I would appreciate if anyone could point me in the right direction.

Any other way to create an install package for vb6 activex document project without prompts?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-23T02:26:09+00:00Added an answer on May 23, 2026 at 2:26 am

    This works for me using MSI to install an ActiveX dll document:

    This reply is a bit late, but I also struggled with this for about
    a year before getting it to work. The key seems to be in registering the ActiveX
    exe or dll when installing on another PC. The following works for me; am only
    listing steps for a dll as still haven’t succeeded 100% with exes:

    1. Create your ActiveX dll Document (you can have forms with dll just like exe)
    2. Use VB Package and Deployment to gather the necessary files in one place.
      Be sure to use the safe VB system files (download a zip file [vb6sp6sys.zip] of them from http://www.jrsoftware.org/iskb.php?vb) in place of those
      generated by VB’s Package and Deployment wizard.
    3. Use VB to create the small executable (make sure Startup Object is
      Sub Main) shown below in the code section. Because Internet Explorer is the “container” for your ActiveX document, this little exe uses a version of it
      (IE) to load your UserDocument1.vbd, DEPENDING ON WHICH OS you are using. Windows 7 and, I assume Vista, use a different version of IE by default, which doesn’t seem to want to run an ActiveX document. But, in their Program Files (x86) there is a version of IE that will – hence the test on whether the (x86) folder exists or not; if not it assumes this is a lower version of Windows and runs using the normal IE. Call this small executable something like “SilentStartUp_ByOS.exe”
    4. Now the bad news: You need to buy Advanced Installer to use its Professional version, which is needed to extract the registration info from
      the native library of your DLL and any included OCXs. There is a free version
      of Advanced Installer, but it doesn’t have this capability.
      Note: There may be other installation packages that will do this also, but
      Advanced Installer is the only one I know about. I’m an Inno fan, but couldn’t
      find any way to do this with Inno.
    5. Include all the files from 2. above, along with the exe created in 3. in
      your Install package. Assign an icon to the exe created in 3. using Advanced
      Installer and make it a shortcut to start your program.
    6. Be sure to install everything (using the Install Parameters screen) in the AppDataFolder\AnyFolderNameHere instead of the ProgramFilesFolder
      for the sake of bypassing Security issues which are very strict on Win7
      and Vista, not to mention if installed on a company intranet.

    When all is done, because your dll was registered, IE should be able
    to start up your ActiveX document.

    Code:

    Sub Main()
    
    Dim strTemp As String
    'ok, it may be Vista or Windows 7...
    strTemp = "C:\Program Files (x86)\Internet Explorer\"
    If CheckFileFolderExists(strTemp, False) = True Then
        'ok, use older version of IEXPLORE to run this on Win7 (or Vista)...
        Shell "C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE " & App.Path & "\UserDocument1.vbd", vbMaximizedFocus
    Else
        Shell "C:\Program Files\Internet Explorer\IEXPLORE.EXE " & App.Path & "\UserDocument1.vbd", vbMaximizedFocus
    End If
    
    End Sub
    
    Function CheckFileFolderExists(strName, fFile) As Boolean
    
    ' The fFile variable determines whether you're
    ' looking for a File (True) or Folder(False)
    ' The strName variable holds the fully qualified
    ' path you're looking for
    
    Dim fso
    Set fso = CreateObject("Scripting.FileSystemObject")
      CheckFileFolderExists = False
    
      If fFile = True Then  ' It's a file
    
        If fso.FileExists(strName) = True Then
          CheckFileFolderExists = True
          Exit Function
        End If
    
      Else  ' It's a folder/directory
    
        If fso.FolderExists(strName) = True Then
          CheckFileFolderExists = True
          Exit Function
        End If
    
      End If
    
      Set fso = Nothing
    
    End Function
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have created an ActiveX dll using VB6 and packaged it using the Package
We have a VB6 project that compiles to an ActiveX EXE that happens to
I have a VB6 ActiveX DLL that has run fine on all our machines
In our project, we have a lot of ActiveX controls written in VB6. On
I have a legacy VB6 ActiveX control used in IE to provide control of
I have a VB6 application implemented as an ActiveX exe. I also have a
I have a VB6 dll that is trying to create a COM object using
I have a VB6 project in Visual Source Safe 6.0. When I open the
I have a VB6 COM component which I need to call from my .Net
I'm try develop an ActiveX Control in VB6. It have one UserControl and one

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.