Click here to Skip to main content
15,896,359 members

File I/O permissions, the C# way

lukeer asked:

Open original thread
Those interested in the why can have a look here[^].
For now, I wonder how to do the following:

During installation with administrative permissions, my software creates a directory within "Documents and Settings\All Users\Documents". Users shall save their projects there.

Normally, users are allowed to create their own files there but not to alter files created by another user. I want to allow users to change all files regardless of creator. This is what I derived from stackoverflow.com[^]
// Create a new DirectoryInfo object.
System.IO.DirectoryInfo dInfo = new System.IO.DirectoryInfo(dirName);

// Get a DirectorySecurity object that represents the
// current security settings.
DirectorySecurity dSecurity = dInfo.GetAccessControl();

// Add the FileSystemAccessRule to the security settings.
dSecurity.AddAccessRule(
    new FileSystemAccessRule(
        new System.Security.Principal.NTAccount("UserGroupGoesHere"),
        FileSystemRights.DeleteSubdirectoriesAndFiles,
        AccessControlType.Allow
    )
);

// Set the new access settings.
dInfo.SetAccessControl(dSecurity);
Maybe, I'll have to repeat permission adaption on every file create for the newly created file. But still the question stands: What is "UserGroupGoesHere" to substitute for? It shall represent all normal users, not excluding power users.

How do I get the name of the "users" user group on any given windows pc?
Tags: C# (C# 2.0)

Plain Text
ASM
ASP
ASP.NET
BASIC
BAT
C#
C++
COBOL
CoffeeScript
CSS
Dart
dbase
F#
FORTRAN
HTML
Java
Javascript
Kotlin
Lua
MIDL
MSIL
ObjectiveC
Pascal
PERL
PHP
PowerShell
Python
Razor
Ruby
Scala
Shell
SLN
SQL
Swift
T4
Terminal
TypeScript
VB
VBScript
XML
YAML

Preview



When answering a question please:
  1. Read the question carefully.
  2. Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
  3. If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
  4. Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.
Let's work to help developers, not make them feel stupid.
Please note that all posts will be submitted under the http://www.codeproject.com/info/cpol10.aspx.



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900