microsoft.public.dotnet.framework.setup

Phil Wilson

5/9/2006 8:41:00 PM

The smartass answer is that you shouldn't be creating files in that folder.
That's what all those Documents&Settings special folders are for - you'd
create a folder in there that's specific to your company and app, create the
files there. Then you can remove that folder at uninstall time with a custom
action. If they're junk, put them in the temp folder and let the users clean
them up in their own time. Ordinary users can't create files in Program
Files - that's the issue, so your app is stuck with requiring elevated
privileges. On Vista practically everyone could be ordinary and the files
will be re-directed away (I don't know where) so you'll have another set of
issues to deal with. So you need an uninstall custom action that removes
the left-over files, and longer term it would be wise to change your app if
you expect it to be installed on Vista.

http://www.windowsecurity.com/articles/Windows-Vista-Principle-Least-Priv...
scroll down to Application Development and Installation Concerns.
--
Phil Wilson [MVP Windows Installer]
----
"Joshua Ellul" <jellul@onvol.net> wrote in message
news:%23JsCO5obGHA.864@TK2MSFTNGP05.phx.gbl...
> Hi There,
>
> Is it possible to delete all files from the installation folder upon the
> user removing the software? Some files that my application created are
> not being removed.
>
> Thanks,
>
> Josh
>