installer class failure

[alexia]

Hi,

I created an installer project which installs my C# application. the
installer using install class.
The problem I am facing is in VISTA.
If I install the application as administrator and than trying to run
it from power user or user, windows retry to install the application.
It actually looking for the msi.

The problem is that the msi installer may not be available or is on a
cd which prevents windows to use the cd because off security issue.

My questions are:
1. Why when I try to run the application from user or power user,
windows search for
msi? Why doesn't it re-run it?
2. In what stage should I execute the manifest, during the
installation from the installer class or when compiling the
application?

Thanks for the help...

 

[alexia]

Hi,

I created an installer project which installs my C# application. the
installer using install class.
The problem I am facing is in VISTA.
If I install the application as administrator and than trying to run
it from power user or user, windows retry to install the application.
It actually looking for the msi.

The problem is that the msi installer may not be available or is on a
cd which prevents windows to use the cd because off security issue.

My questions are:
1. Why when I try to run the application from user or power user,
windows search for
    msi? Why doesn't it re-run it?
2. In what stage should I execute the manifest, during the
installation from the installer class or when compiling the
application?

Thanks for the help...

forgot to mention that the install application is a visual studio 2005
set-up project

 

[Family Tree Mike]

Hi,

I created an installer project which installs my C# application. the
installer using install class.
The problem I am facing is in VISTA.
If I install the application as administrator and than trying to run
it from power user or user, windows retry to install the application.
It actually looking for the msi.

The problem is that the msi installer may not be available or is on a
cd which prevents windows to use the cd because off security issue.

My questions are:
1. Why when I try to run the application from user or power user,
windows search for
msi? Why doesn't it re-run it?
2. In what stage should I execute the manifest, during the
installation from the installer class or when compiling the
application?

Thanks for the help...

It sounds like the install has a particular file that is installed and
marked as "vital" in the properties. If a file is missing, it will try and
fix the install. This scenario can happen if you have a custom action with
a template file that is installed and removed in a custome action.

 

[alexia]

It sounds like the install has a particular file that is installed and
marked as "vital" in the properties.  If a file is missing, it will tryand
fix the install.  This scenario can happen if you have a custom action with
a template file that is installed and removed in a custome action.

Hi Mike,

I have two custom actions. Install and uninstall and both run
installer class output.
One of the things that the installer class does is to install driver
by running exe file (installer for the driver compiled by innosetup).
The installer also run manifest file.

what do you mean by saying vital file? all files are vital. I do
exclode some.

Thanks.

 

[Family Tree Mike]

Hi Mike,

I have two custom actions. Install and uninstall and both run
installer class output.
One of the things that the installer class does is to install driver
by running exe file (installer for the driver compiled by innosetup).
The installer also run manifest file.

what do you mean by saying vital file? all files are vital. I do
exclode some.

Thanks.

I have added files to the setup, such as demo files. If those files are
deleted at some point, but the setup project has the property named "Vital"
set to "True" for the demo file, the installer will try to repair them when
the user runs the application.

What do you mean when you say the install custom action runs the installer
class output? I could see your custom action running the innosetup
executable for the driver. Maybe that is what you meant.

 

[alexia]

I have added files to the setup, such as demo files.  If those files are
deleted at some point, but the setup project has the property named "Vital"
set to "True" for the demo file, the installer will try to repair them when
the user runs the application.

What do you mean when you say the install custom action runs the installer
class output?  I could see your custom action running the innosetup
executable for the driver.  Maybe that is what you meant.

I added to the setup project, installer class project. in the custom
actions for the installer (install and uninstall) I run the installer
class,
The installer class on install action installs usb device driver. the
device driver installation is in exe file generated by innosetup.
Do you think that the inno setup exe causes the msi to reinstall?
Why would it try to reinstall, if I already installed it on
administrator user?

 

[Family Tree Mike]

I added to the setup project, installer class project. in the custom
actions for the installer (install and uninstall) I run the installer
class,
The installer class on install action installs usb device driver. the
device driver installation is in exe file generated by innosetup.
Do you think that the inno setup exe causes the msi to reinstall?
Why would it try to reinstall, if I already installed it on
administrator user?

As an experiment, I would recommend trying to create an installer without
the driver for the USB drive, and preinstall the driver on a machine, then
install your product. This should confirm if somehow the custom
action/driver is causing the issue.

 

[alexia]

As an experiment, I would recommend trying to create an installer without
the driver for the USB drive, and preinstall the driver on a machine, then
install your product.  This should confirm if somehow the custom
action/driver is causing the issue.

Thanks, I'll give it a try, though it is werid why windows need to
reinstall the driver if it is already installed.
If I use cpp application instead of the C# installer class, it doesn't
happen. It looks like windows doesn't "like" the installer class.
Anyway, thanks for the help. I'll post my findings here when I have
some.