Does my application in the Local Application Data folder fix any flaws?

Question

We are currently planning to do the installation process for the .NET application. I sell smoother (reading: “possible”) for non-admin users, I came across applications like Google Chrome and Microsoft SkyDrive:

They do not seem to be installed in the regular "Program Files" folder, but instead in the "Local Application Data" folder of the current user.

Since this folder is intended for each user, it is writable by the current user, and no administrative permissions are required for recording.

I managed to change the configuration of NSIS to work and install in this folder correctly, but I'm still not sure if this is good practice and may or may not have flaws.

My question is:

Do you have any recommendations for installing or not installing in the Local Application Data folder?

(I hope this question is sufficient for programming so that it can be saved here)

Answer 1

It's not clear from your question, but you should install the program in $ LocalAppdata \ Programs, not just $ LocalAppData (FOLDERID_UserProgramFiles constant in Win7)

I know that I like applications that can be installed as a non-admin, at least you know that the application does not require a driver or that it gets confused with the configuration of the machine in other ways.

Some people prefer to make a system-wide installation and give the user this option is not so difficult in NSIS:

• RequestExecutionLevel highest
• Add a user page with two radio buttons (Just Me and All Users) and leave the selection gray throughout the computer if the user is not an administrator ( UserInfo plugin)
• Install $Instdir and SetShellVarContext based on installation mode
• Use SHCTX as a HKEY registry

Some IT / domain administrators may be unhappy if their users can install the material, this is the only minus I can come up with, but they should block the system properly if they think this is a problem IMHO ...