Pieter,
When an application is first installed, even under an administrative
account, any files that need to be registered are normally only registered
for the admin account, even though it's installed for Everyone. The first
time the application is started under another login, the .msi then needs to
register the files for that login. As far as I'm aware, there is no way to
circumvent this action from occuring, though I'm sure if there is, one of
the more learned folk that frequent the group will enlighten us. :)
If this occurs each time the application is started under the same login,
then there may be a problem with the installer package? I know of an issue
with MS Security and InstallShield where a CD installation is prevented from
writing the .msi file to the Windows directory. The workaround is to build
the application as a web-based installation and the .msi file will be
properly placed where it belongs. Hope this helps
"Pieter" <pi****************@hotmail.comwrote in message
news:uI**************@TK2MSFTNGP03.phx.gbl...
Hi,
Two VB.NET Windows Forms (2.0) applications had the same behaviour when
they were run the first time by a user: after clicking on the shortcut,
the location of the MSI-file is asked, and a part of the installation is
(re)done.
What can I do to stop this behaviour? It was isntalled by an
adminsitrator-account, for 'Everyone', and should work?
Thanks a lot in advance,
Pieter
