I have a .Net application I have developed. I am using a VStudio 2003 Setup
Project to build the setup and msi files. The app requires administrative
access to install. During the setup process I solicit some information in
the setup dialog boxes which is then written to
HKLM/Software/Manufacturer/AppName by the setup program. The app is
installed for "Everyone". This all works fine.
Then we have the user logon to the PC. The application icon is on their
desktop. However, when they click on the icon a dialog box appears saying
"Installing". It of course fails because the app was installed from a CD
which is no longer in the drive. If I copy my setup/msi files to the hard
drive and install from there the "Installation" will complete. However,
during this so called "Installation" it erases some of my registry entries
put in by the original administrative installer. I guess Microsoft considers
this a "Feature" of their repair process.
1. What is the proper way to deploy something like this. I note that some
apps put their msi files in the temp directory. Seems like a real waste of
space if you have a large application.
2. Where is it documented? (Don't just say MSDN, you can sift through
thousand of pages before you find all you need)
[MSFT] - 27 Jun 2005 03:38 GMT
Hello,
Is it possible to save the configaration data in
HKCU/Software/Manufacturer/AppName, so that every user can have own copy. I
am not sure if there is a document about this. I suggest you may post this
issue in microsoft.public.platformsdk.msi. You may be luck to find more
helpful information there.
Luke
Norsoft - 27 Jun 2005 14:54 GMT
Thanks!, I have started moving everything to HKU at install which I believe
will move them to HKCU when the user logs on. There just doesn't seem to be
any good documentation on proper setup procedures. Thanks also for pointing
me to the other group. I was hoping someone would know where the correct
place to ask this was.
Pete
> Hello,
>
[quoted text clipped - 6 lines]
>
> Luke