Exactly, when going to use a shortcut in the start menu, first you get
the MSI installer "installing" status box, and then you usually get
prompted for the installation location, for the original path is not
available.
This seems to happen when the product is installed by the admin (The
install is done using the "Everyone" setting provided in the Visual
Studio installer dialog). After the install is done, the machine has
a user account added (which has admin priv) and then logging in as the
new user. The advertize thing happens during use in the new user
account.
[quoted text, click to view] "Chua Wen Ching" <chua_wen_ching@nospam.hotmail.com> wrote in message news:<CC87222C-FCF6-4401-BB17-0BF3C4BFC27B@microsoft.com>...
> Hi Joe,
>
> Can you elaborate more with this phrase?
>
> Everything runs ok, but when you go to use the app installed by
> somesetup.msi, it has been installed as advertise and not actually
> installed.
>
> --> Can you provide some sample screenshots? What does it means by installed
> as advertise? Do you mean, when you open Visual Studio .NET, it seems that
> there is a loading bar window.. loading it like initializing an install..
> something like that?
>
> Thanks.
>
> "Joe Goeke" wrote:
>
> > Has anyone seen strange behaviour of installing using the .msi
> > association? We have been seeing our setups being installed in the
> > advertise mode when running them from a script file using the .msi
> > association way of running them. ie, we use the following commandline
> > style in a bat file to automatically install our apps:
> >
> > start/wait %systemdrive%\path\somesetup.msi /qn
> >
> > Everything runs ok, but when you go to use the app installed by
> > somesetup.msi, it has been installed as advertise and not actually
> > installed.
> >
> > This only happens with the msi setups we have developed. They are all
> > made using the Visual Studio Installer.
> >
> > Any ideas why? Are there any special setting somewhere that could
> > cause this?
> >
> > Thanks in advance!
> > ---JHG
