Hi,
I am having this problem for sometime and not sure what's the problem is with my MSI. I created an MSI using VS.NET 2005 for my application. The MSI created just fine. I ran the MSI file on my user machine using my adminstrator account, select the option install to all user. The installation ran fine and I was able open and run program ok; however, when my user, who doesn't have the admin permission, log in and run my program via shortcut created by the MSI - he get the installation prompt saying it wants the MSI. The problem doesn't happen when he browse to the folder where the exe and double click on the exe.
What am I missing? I thought this problem only happen if I am not select the option to all user.
Thanks in advance

---

Phil (UWMC DB Specialist)

Hi Philly2,

I am moving this thread from Base ".NET FrameworkSetup" forum to the "ClickOnce and Setup & Deployment Projects" forum, since the issue is related to deployment. There are more deployment experts in the "ClickOnce and Setup & Deployment Projects" forum.

Thanks

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Hi Philly2,

Do you need to write some register key to the HKEY_CURRENT_USER node? So when the application is run under another account, it cannot find these register information and want to install it again.

Sincerely,
Kira Qian

---

Please mark the replies as answers if they help and unmark if they don't.

Kira,
Thanks for your reply, yes I do have to write some reg to HKEY_CURRENT_USER; My work around of problem is to check the reg; if it doesn't exists, then create one under this user account. The applicatin works fine ifthe userdouble click on the Exe itselft the first time. It doesn't work if the user click on the Application shortcut that created by the MSI. I am wonder if there is any special configuration about the shortcut?

---

Phil (UWMC DB Specialist)

Shortcuts are special - they link to an MSI API call that locates the target file and does a repair if it's missing.

I don't think the issue is likely to be a registry entry because registry entries are in the cached MSI file in \Windows\installer. If it needs the original MSI file then it most likely wants to install a file. That can happen if you have installed a file into a user-specific location (My Documents, for example).

---

Phil Wilson

Hi PhilWilson,
My install files in the target machine are in c:\program files\]product name]\[application name]. There isn't any file store in user specific location.
Thanks

---

Phil (UWMC DB Specialist)