Installer question: Read-only files

  • Thread starter Thread starter Michael A. Covington
  • Start date Start date
M

Michael A. Covington

I want to deploy a project in which the user is provided with a set of
READ-ONLY files to use as templates. They will be in a directory to which
the user can add files of his own.

It's important to keep the user from deleting any of the pre-supplied files,
because if this is done, the Windows Installer apparently wants to "repair"
the application. I didn't realize it kept track of such things, but it's
doing so.

How can I make the files install as read-only files?

Making them read-only in the source directory isn't enough.

If this is a Custom Action, how can I determine the directory (under Program
Files) in which they are installed? For example, suppose the Custom Action
were just a .BAT file. Could it use environment variables to find out where
the user has installed the application?


Thanks!
 
Ayende Rahien said:
Just use CACLS to deny him the right to delete the files.
Click to expand...

How? When? How do I build this into a deployment project? How would CACLS
know where the user chose to install the application?

In any case, I found that all I have to do is View File System (in the
deployment project) and mark the files read-only there.
 
Back
Top