PDA

View Full Version : Warning 4350 - Dynamic Scan



NewsArchive
05-08-2001, 12:00 AM
Swann,
I too am getting annoying "-4095 Warnings." 140 X "-4095 warnings"
everytime that I build my project. The project works fine.

I submitted the request to installshield as a bug because as far as I am
concerned I do not require a "Warning" which informs me of something I
already know while having to sift through my build status to find the error
messages that are applicable. I am not using SOURCEDIR, TARGETDIR or any of
the other issues the warning suggests.
Predictably the InstallShield Response:

"The 4095 warning message is not a bug with InstallShield for Windows
Installer. This warning's purpose is to make you aware that certain
InstallScript custom actions may not work when called from a DoAction event,
blah, give us your money, we might be able to help, money"

If this warning is only triggered by InstallScript CA's maybe you could
rewrite your CA in Visual Basic, embedded in a custom action. Not ideal if
you have large CA I Know.

Dave

Stephen Beaulieu <sbeaulieu@eprise.com> wrote in message
news:3af69df9$1@12.41.20.38...
> Does your CA work? The warning is help people who might be using DoAction
> incorrectly. If your CA works, then the warning doesn't apply to you. If
> your CA didn't work and there was no warning you would probably be writing
> about how IS should put in a warning during the build.
>
>
> "Swann" <swann5@hotmail.com> wrote in message news:3af67845@12.41.20.38...
> > Hello, I have a following problem. My WI-based setup needs to detect and
> > uninstall a previous legacy installation. If a previous version is
found,
> > the setup displays a custom dialog, asking the user to confirm removal
of
> > the previously installed application prior to installing the existing
one.
> > After getting the user confirmation, I run InstallScript CA (launching
it
> > from this custom dialog), which checks whether some files of the
> previously
> > installed application are currently in use.
> >
> > My problem is that the setup build displays Warning 4095 ("Calling
> DoAction
> > from a control event on an InstallScript custom action may not work in
all
> > cases, especially if you are using SOURCEDIR, TARGETDIR,
> > PreShowComponentDlg, or MsiDoAction in the script"), although I launch
the
> > CA from the dialog in question, as it is described in the "Launch a
Custom
> > Action from a Dialog" IPWI Help.
> > Thus, I would like to ask if InstallShield can change the build
procedure
> so
> > that setting Doaction in a a dialog would not inevitably produce a build
> > warning (at least if SOURCEDIR, TARGETDIR, PreShowComponentDlg, or
> > MsiDoAction are not used in the script).
> >
> > Of course, I could launch this CA during the setup initialization, but I
> am
> > concerned with the scenario, when the user closes the active application
> > after viewing a couple of initial dialogs.
> >
> > Can anybody help me to resolve this problem?
> >
> > TIA,
> >
> > Swann
> >
> >
> >
>
>

NewsArchive
05-08-2001, 12:00 AM
Swann,
I too am getting annoying "-4095 Warnings." 140 X "-4095 warnings"
everytime that I build my project. The project works fine.

I submitted the request to installshield as a bug because as far as I am
concerned I do not require a "Warning" which informs me of something I
already know while having to sift through my build status to find the error
messages that are applicable. I am not using SOURCEDIR, TARGETDIR or any of
the other issues the warning suggests.
Predictably the InstallShield Response:

"The 4095 warning message is not a bug with InstallShield for Windows
Installer. This warning's purpose is to make you aware that certain
InstallScript custom actions may not work when called from a DoAction event,
blah, give us your money, we might be able to help, money"

If this warning is only triggered by InstallScript CA's maybe you could
rewrite your CA in Visual Basic, embedded in a custom action. Not ideal if
you have large CA I Know.

Dave

Stephen Beaulieu <sbeaulieu@eprise.com> wrote in message
news:3af69df9$1@12.41.20.38...
> Does your CA work? The warning is help people who might be using DoAction
> incorrectly. If your CA works, then the warning doesn't apply to you. If
> your CA didn't work and there was no warning you would probably be writing
> about how IS should put in a warning during the build.
>
>
> "Swann" <swann5@hotmail.com> wrote in message news:3af67845@12.41.20.38...
> > Hello, I have a following problem. My WI-based setup needs to detect and
> > uninstall a previous legacy installation. If a previous version is
found,
> > the setup displays a custom dialog, asking the user to confirm removal
of
> > the previously installed application prior to installing the existing
one.
> > After getting the user confirmation, I run InstallScript CA (launching
it
> > from this custom dialog), which checks whether some files of the
> previously
> > installed application are currently in use.
> >
> > My problem is that the setup build displays Warning 4095 ("Calling
> DoAction
> > from a control event on an InstallScript custom action may not work in
all
> > cases, especially if you are using SOURCEDIR, TARGETDIR,
> > PreShowComponentDlg, or MsiDoAction in the script"), although I launch
the
> > CA from the dialog in question, as it is described in the "Launch a
Custom
> > Action from a Dialog" IPWI Help.
> > Thus, I would like to ask if InstallShield can change the build
procedure
> so
> > that setting Doaction in a a dialog would not inevitably produce a build
> > warning (at least if SOURCEDIR, TARGETDIR, PreShowComponentDlg, or
> > MsiDoAction are not used in the script).
> >
> > Of course, I could launch this CA during the setup initialization, but I
> am
> > concerned with the scenario, when the user closes the active application
> > after viewing a couple of initial dialogs.
> >
> > Can anybody help me to resolve this problem?
> >
> > TIA,
> >
> > Swann
> >
> >
> >
>
>

alecava
02-15-2002, 09:12 AM
I'd like to use the dynamic scan of my components so I sat the check box for the dynamic scan, but, when I try to build my project I obtain the following wanrnig for about the 80% of my dll.
I tried to delete manually all the entries in the registry item and in the COM registration for all those components, but this message still appears. I looked at the registry table to be sure that no entries are present for that components but nothing....

Thanks in advance


** Warning: -4350: Dynamically acquired ProgId CSView.Application conflicts with static data associated with component CSView.dll. Overwriting with dynamic data.
New ProgId CSView.Application dynamically acquired for component CSView.dll
New ProgId Config.Application dynamically acquired for component Config.dll
** Warning: -4350: Dynamically acquired ProgId GetRefl.Application conflicts with static data associated with component GetRefl.dll. Overwriting with dynamic data.

Joshua
02-15-2002, 06:30 PM
Alessandro,

This will occur if you do the following:

1. Use the Component Wizard to scan in your files that contain COM info
2. Set your Component to "Extract at Build"

If you do both of these options, these warnings will occur during build because your "Extract at Build" option is trying to overwrite the data already put there by the Component Wizard.

I would recommend doing one or the other, both are not necessary.

I hope this helps!

Regards,

Joshua
InstallShield