Re: file installation order

Tech-Archive recommends: Fix windows errors by optimizing your registry

That makes sense, and yes it was set to vsdrfCOMSelfReg.

Thanks a lot for your help.

"Phil Wilson" wrote:

> In the VS setup project, in the properties of those OCXs, what was your
> Register property set to? I suspect it was vsdrfCOMSelfReg, which requires
> install-time registration and loading of your OCX, so its dependencies need
> to be present. If you use vsdrfCOM, the registration entries are extracted
> at build time, and at install time the registry entries are written from the
> MSI file and the OCX copied to the system, effectively the same as
> self-registration except that the OCX doesn't need to be loaded and called.
> --
> Phil Wilson
> [Microsoft MVP-Windows Installer]
> Definitive Guide to Windows Installer
> http://apress.com/book/bookDisplay.html?bID=280
>
> "MikeWorkflow" <MikeWorkflow@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:2CEBC1AA-D328-4CE1-8E6A-900EFA0BE7D1@xxxxxxxxxxxxxxxx
> > Greetings,
> >
> > I have a pretty straight forward installation file that includes a couple
> > OCX and DLLs that rely on MS VC++ runtime libraries. I've included the
> > merge
> > modules in the setup file to copy these necessary libraries to the user's
> > system.
> >
> > I of course need to register the OCXs when installing, and the OCXs cannot
> > be registered unless those runtime files are included.
> >
> > I build my setup MSI and run it on a machine and it works fine.
> >
> > However, another user tried running this MSI and the installer indicated
> > that it was unable to register my OCXs. I told them to ignore so they
> > could
> > finish the install, then run the setup again. The second time they ran it,
> > the OCXs were registered properly.
> >
> > This would indicate to me that the OCX files were copied and the installer
> > attempted to register them BEFORE the runtime libraries were copied out.
> >
> > In Visual Studio, the project can detect dependancies but this doesn't
> > help
> > me unless the merge module explicitly states a dependency or it detects
> > the
> > dependency from another VS project. Just trying to package up loose files
> > doesn't seem to leave me with an option to say "hey, make sure this file
> > is
> > installed before this one".
> >
> > Is there any way, either in my VS.NET setup project or using soemthing
> > like
> > ORCA, to ensure that those runtime libraries are copied out BEFORE my OCX
> > files?
>
>
>
.

Relevant Pages

  • Re: Installing Assemblies and Registering OCX
    ... If you start a setup project and just ... create folders off Application Folder you'll see how it works. ... Registering an OCX - the file properties have a Register property. ... Phil Wilson [MVP Windows Installer] ...
    (microsoft.public.vsnet.setup)
  • Re: VS 2005 Setup Project: Howto determine startup path of setup.e
    ... my "normal" setup of course does the registrations itself. ... runs on the server and installs the DLLs let's say in ... register the DLLs on the client. ... Definitive Guide to Windows Installer ...
    (microsoft.public.vsnet.setup)
  • Re: file installation order
    ... In the VS setup project, in the properties of those OCXs, what was your ... Register property set to? ... MSI file and the OCX copied to the system, ... Definitive Guide to Windows Installer ...
    (microsoft.public.dotnet.framework.setup)
  • file installation order
    ... OCX and DLLs that rely on MS VC++ runtime libraries. ... I of course need to register the OCXs when installing, ... This would indicate to me that the OCX files were copied and the installer ...
    (microsoft.public.dotnet.framework.setup)
  • Re: Installing Assemblies and Registering OCX
    ... I needed a setup becuase my data folders are ... create folders off Application Folder you'll see how it works. ... Registering an OCX - the file properties have a Register property. ... Phil Wilson [MVP Windows Installer] ...
    (microsoft.public.vsnet.setup)