FileSystemAclExtensions Missing forced SetAccessControl methods

[AliveDevil]

Current implementation of FileSystemAclExtensions.SetAccessControl only works one time - the first time after it has been edited, and then applied to one file or directory.

runtime/src/libraries/System.IO.FileSystem.AccessControl/src/System/Security/AccessControl/FileSystemSecurity.cs

Lines 117 to 131 in 50c4cb9

	internal void Persist(string fullPath)
	{
	WriteLock();
	try
	{
	AccessControlSections persistRules = GetAccessControlSectionsFromChanges();
	base.Persist(fullPath, persistRules);
	OwnerModified = GroupModified = AuditRulesModified = AccessRulesModified = false;
	}
	finally
	{
	WriteUnlock();
	}
	}

The first call to Persist through SetAccessControl successfully applied all modified sections, but reusing the same FileSystemSecurity object on another FileSystemItem doesn't apply anything, because GetAccessControlSectionsFromChanges returns "None" - thus subsequent calls to Persist are unusable.

Please provide an overload SetAccessControl(string path, AccessControlSections sections) to apply the same FileSystemSecurity object to multiple FileSystemItems, without having to recreate or modify the FileSystemSecurity object just for the "Changed"-flag.

[huoyaoyuan]

For feature request of new API, you can file an issue of API Proposal.