"Phani" <pyarlaga@inovant.com> wrote in message
news:0b9f01c3bba1$a57bf940$a001280a@phx.gbl...
> Hi,
>
> Yes you are right it asks for the MSI file and not the
> setup.exe and this re-install happens only the first time
> the user logs in and after that it is fine.
>
> My Question is there are two other applications which we
> built using setup and deployment project which are not
> behaving this way.The re-install doesnot happen for those
> two apps when another user logs into the same machine for
> the first time.
>
> To let you know,I am not putting any entries into HKCU
> instead I am putting the entries into HKLM(Local Machine)
> in the registry.
>
> My problem is the Administartor will login and install
> this application on all the user's machine during the
> weekend from a network path.Monday morning the user's will
> login and access this application if the re-install starts
> then they will not know anything about the registry
> entries that we prompt during the install so the re-
> install should not happen at any cost.Moreover the admin
> will install from the network path which the user might
> not have access to the MSI file path.
>
> Do you have any suggestions on how to ovecome this.Is
> there any setting in the project that i should do so that
> the windows installer will cache the MSI file.
>
> I would appreciate if you could suggest me something on
> this.
>
> Thanks
> Phani
>
> >-----Original Message-----
> >It shouldn't be asking for the setup.exe, but it might be
> asking for the MSI
> >file. It's always a good idea to have the MSI file
> available for repair etc. The
> >interesting question is whether this happens just once
> for each new user, and if
> >the anser is yes then the behavior is normal. If you
> install for a specific
> >user, and when you have HKCU registry entries being
> installed, then the HKCU
> >entries need creating each time a new account uses them,
> and the only place they
> >can be installed from is the MSI file. There *might* be
> something going on with
> >files that are going to a user-specific location because
> registry entries can
> >usually be obtained from the cahed MSI file in
> Windows\installer, and it
> >typically only needs the source if files need to be added.
> >--
> >Phil Wilson [MVP Windows Installer]
> >----
> >"Phani" <anonymous@discussions.microsoft.com> wrote in
> message
> >news:026701c3bb80$d50309e0$a501280a@phx.gbl...
> >> Thanks for your reply..
> >>
> >> I had installed it for "Everyone" and not "Just me"
> >> To let you know more about this.I have a custom install
> >> and I update the windows registry during the install.
> >>
> >> >-----Original Message-----
> >> >You might have installed this for "Just Me" instead
> >> of "Everyone". Just me is
> >> >the default, and that makes it belong to only the admin
> >> user that installed it.
> >> >It must be installed for Everyone for other users to
> >> access it.
> >> >--
> >> >Phil Wilson [MVP Windows Installer]
> >> >----
> >> >"Phani" <pyarlaga@inovant.com> wrote in message
> >> >news:057501c3bacc$ca105ab0$a301280a@phx.gbl...
> >> >> Hi all,
> >> >>
> >> >> I have created a setup project using dotnet setup &
> >> >> deployment project for one of our applications.
> >> >>
> >> >> I installed this application logged in as an admin
> user
> >> of
> >> >> the box and checked the application, every thing was
> >> fine.
> >> >>
> >> >> I logedoff and another user who is also an admin of
> this
> >> >> box logs in and clicked on the desktop icon of this
> >> >> application, windows installer kicks off and starts
> the
> >> >> install process again and at some point it asks for
> the
> >> >> actual application setup.exe
> >> >>
> >> >> Could some one help me in solving this problem.How
> can I
> >> >> avoid this re-install if another user logins on the
> same
> >> >> machine.
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >