Setup reruns for each new user of an application?

[Byron]

I have a Windows form application developed in VS 2003 C# I am using
Installshield to install it. After running Setup, each time a new user runs
the application for the first time Setup attempts to run. I thought I had
run this down before as being a file set with AlwaysCreate = true in the
setup project, but the only change I've made is to add a Word DOC file in the
setup (just copying it, not opening it) and I can't find any instances of
AlwaysCreate = true.

Can anybody tell me what might be causing this? Thanks in advance for any
help.

[Ken Halter]

Byron wrote:

Can anybody tell me what might be causing this? Thanks in advance for any
help.

I'm not a ".Net" guy but... can't you tell InstallShield you want to
install to "All Users"? We've used InstallShield Express for years
(upgraded to AdminStudio just last week) and we normally just tell the
end users to install to "All Users".

The thing is, the Windows Installer service monitors your app during
startup. If there's even the slightest problem (missing reg entry for
that user, missing file, wrong permissions on a file, etc, etc), setup
will start again and attempt to Repair itself.

The confusing part is... since I'm a "VB Classic guy", the components I
require are shared with Office/etc. That means if the end user
uninstalls Office or does anything related to any of the components I've
installed or Office has installed, the Repair starts no matter if it's
my app they're starting or some Office app.

I've written a Custom Action in VB6 that "copies" misc. files to various
folders instead of letting Windows Installer do it. The reason for that
was... we have a few "default" files that generally get deleted after
everything's setup and running for a week or two. If we let
InstallShield "install" those files, when the end user deletes those
files, setup will "repair" them right back. Since I'm just copying them,
the Windows Installer service doesn't care what happens to them.

--
Ken Halter - MS-MVP-VB - http://www.vbsight.com
Please keep all discussions in the groups..

[Ken Halter]

Byron wrote:

Can anybody tell me what might be causing this? Thanks in advance for any
help.

I'm not a ".Net" guy but... can't you tell InstallShield you want to
install to "All Users"? We've used InstallShield Express for years
(upgraded to AdminStudio just last week) and we normally just tell the
end users to install to "All Users".

The thing is, the Windows Installer service monitors your app during
startup. If there's even the slightest problem (missing reg entry for
that user, missing file, wrong permissions on a file, etc, etc), setup
will start again and attempt to Repair itself.

The confusing part is... since I'm a "VB Classic guy", the components I
require are shared with Office/etc. That means if the end user
uninstalls Office or does anything related to any of the components I've
installed or Office has installed, the Repair starts no matter if it's
my app they're starting or some Office app.

I've written a Custom Action in VB6 that "copies" misc. files to various
folders instead of letting Windows Installer do it. The reason for that
was... we have a few "default" files that generally get deleted after
everything's setup and running for a week or two. If we let
InstallShield "install" those files, when the end user deletes those
files, setup will "repair" them right back. Since I'm just copying them,
the Windows Installer service doesn't care what happens to them.

--
Ken Halter - MS-MVP-VB - http://www.vbsight.com
Please keep all discussions in the groups..

[Byron]

Thanks for the reply, but I am selecting Everyone when I install and the
re-run of setup even happens when I immediately run the application as the
same user I just installed as.

"Ken Halter" wrote:

Byron wrote:

Can anybody tell me what might be causing this? Thanks in advance for any
help.

I'm not a ".Net" guy but... can't you tell InstallShield you want to
install to "All Users"? We've used InstallShield Express for years
(upgraded to AdminStudio just last week) and we normally just tell the
end users to install to "All Users".

The thing is, the Windows Installer service monitors your app during
startup. If there's even the slightest problem (missing reg entry for
that user, missing file, wrong permissions on a file, etc, etc), setup
will start again and attempt to Repair itself.

The confusing part is... since I'm a "VB Classic guy", the components I
require are shared with Office/etc. That means if the end user
uninstalls Office or does anything related to any of the components I've
installed or Office has installed, the Repair starts no matter if it's
my app they're starting or some Office app.

I've written a Custom Action in VB6 that "copies" misc. files to various
folders instead of letting Windows Installer do it. The reason for that
was... we have a few "default" files that generally get deleted after
everything's setup and running for a week or two. If we let
InstallShield "install" those files, when the end user deletes those
files, setup will "repair" them right back. Since I'm just copying them,
the Windows Installer service doesn't care what happens to them.

--
Ken Halter - MS-MVP-VB - http://www.vbsight.com
Please keep all discussions in the groups..

[Byron]

Thanks for the reply, but I am selecting Everyone when I install and the
re-run of setup even happens when I immediately run the application as the
same user I just installed as.

"Ken Halter" wrote:

Byron wrote:

Can anybody tell me what might be causing this? Thanks in advance for any
help.

I'm not a ".Net" guy but... can't you tell InstallShield you want to
install to "All Users"? We've used InstallShield Express for years
(upgraded to AdminStudio just last week) and we normally just tell the
end users to install to "All Users".

The thing is, the Windows Installer service monitors your app during
startup. If there's even the slightest problem (missing reg entry for
that user, missing file, wrong permissions on a file, etc, etc), setup
will start again and attempt to Repair itself.

The confusing part is... since I'm a "VB Classic guy", the components I
require are shared with Office/etc. That means if the end user
uninstalls Office or does anything related to any of the components I've
installed or Office has installed, the Repair starts no matter if it's
my app they're starting or some Office app.

I've written a Custom Action in VB6 that "copies" misc. files to various
folders instead of letting Windows Installer do it. The reason for that
was... we have a few "default" files that generally get deleted after
everything's setup and running for a week or two. If we let
InstallShield "install" those files, when the end user deletes those
files, setup will "repair" them right back. Since I'm just copying them,
the Windows Installer service doesn't care what happens to them.

--
Ken Halter - MS-MVP-VB - http://www.vbsight.com
Please keep all discussions in the groups..